dotnet / dotnet/aspnetcore

[dnceng-bot] Branch `aspnetcore/release/9.0` can't be merged to Azdo internal branch

Closed
#69,185 1 comment 0 reactions 0 assignees View on GitHub
area-infrastructure
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

Branch [release/9.0](https://github.com/dotnet/aspnetcore/commits/release/9.0/) in `dotnet/aspnetcore` repo can't be mirrored from GitHub to Azure [internal/release/9.0](https://dev.azure.com/dnceng/internal/_git/dotnet-aspnetcore?version=GBinternal%2Frelease%2F9.0&_a=history) via internal merge.

There are conflicting commits in the target branch.
The branch is configured to be mirrored via automated merge.
The situation is rare but normal. The target branch is expected to receive manual commits in the Azure DevOps clone, which could cause conflict.

Conflicts need to be **resolved to unblock the code flow**.

- you can resolve the issue by resolving the conflict in the **target branch only**.
- Please make sure that the changes sensitive from security perspective are not published ahead of time to GitHub!
- reverting the extra commits in the Azdo target branch.
- checking the logs of the mirroring process in the [mirroring pipeline](https://dev.azure.com/dnceng/internal/_build?definitionId=1387).
- you can disable the mirroring of the branch in the [configuration file](https://dev.azure.com/dnceng/internal/_git/dotnet-mirroring?path=/dnceng-subscriptions.jsonc).
- you can ask @dotnet/dnceng for help or read the [documentation](https://dev.azure.com/dnceng/internal/_git/dotnet-mirroring?path=/README.md).

Please close this issue once the conflict is resolved.

Contributor guide

Open the contributing guide

Research direction

Start by checking the mirroring pipeline (definitionId 1387) and the history of the internal/release/9.0 target branch. Read the dotnet-mirroring README.md and dnceng-subscriptions.jsonc before taking action. Resolve or revert the target-branch conflict without publishing security-sensitive changes to GitHub, then close the issue once mirroring is unblocked.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, git
Domain
ci-cd, devops, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.