Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
#673 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, csharp
Domain
ci-cd, devops

Research direction

Start by reproducing the extractor pipeline in the affected Azure DevOps repository and compare its successful artifacts with the missing branch and pull request. Trace the extractor pipeline's branch and pull-request creation step; done means a run creates both in that repository.

Written by the indexing model from the issue text.

Description

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

.

Dominant language
C#
Stars
448
Forks
247
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/apiops

All issues in Azure/apiops

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.