Azure / apiops

APIOps applies the concepts of GitOps and DevOps to API deployment. By using practices from these two methodologies, APIOps can enable everyone involved in the lifecycle of API design, development, and deployment with self-service and automated tools to ensure the quality of the specifications and APIs that they’re building.
https://azure.github.io/apiops
MIT License
328 stars 193 forks source link

[BUG] Extractor pipeline is not working only in 1 specific repo #673

Open sandhya-techie opened 1 month ago

sandhya-techie commented 1 month ago

Release version

v6.0.1.1

Describe the bug

The pipeline is running successfully, but it is not creating a new branch or pull request in the repository. image I have verified repository has all permission in place image

Expected behavior

After running the extractor pipeline, it should create a new branch and also generate a pull request.

Actual behavior

The pipeline has run successfully, and I can confirm that the artifacts are visible in the extractor pipeline as well. image image

I am not sure why new branch is not getting created in ado repo

Reproduction Steps

.

github-actions[bot] commented 1 month ago
  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.
sandhya-techie commented 1 month ago

@guythetechie , @waelkdouh The repository was created with a .gitignore file: Visual Studio, which is causing an issue: despite the pipeline running successfully, it does not create a new branch or pull request.

guythetechie commented 1 month ago

@sandhya-techie - we've seen strange issues like this with ADO in the past (see #170).

Can you paste the full output of the last step in your extractor pipeline? Your screenshot got cut off after Creating artifacts folder...