dotnet / dotnet/maui

[dnceng-bot] Branch `maui/inflight/candidate` can't be mirrored to Azdo fast forward branch

Open
#35,875 0 comments 1 reaction 0 assignees View on GitHub
area-infrastructure
Dominant language
C#
Stars
23.3k
Forks
2k
Avg merge
1d 15h
Merged PRs (30d)
290

Description

Branch [inflight/candidate](https://github.com/dotnet/maui/commits/inflight/candidate/) in `dotnet/maui` repo can't be mirrored from GitHub to Azure DevOps [inflight/candidate](https://dev.azure.com/dnceng/internal/_git/dotnet-maui?version=GBinflight%2Fcandidate&_a=history) via fast forward.
There are unexpected commits in the target branch.
The branch is configured to be mirrored via fast forward only and is not expected to receive commits in the Azure DevOps clone.

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

You can resolve the issue by unifying the SHA of the branches:
- merging the extra commits from the Azdo target branch into the source branch and pushing the changes to GitHub.
- Please make sure that the changes are not sensitive from security perspective!
- 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 problem is resolved.

Contributor guide

Open the contributing guide

Research direction

Start by comparing the GitHub and Azure DevOps SHAs for inflight/candidate, then inspect the mirroring pipeline logs (definition 1387). Read the dotnet-mirroring README and dnceng-subscriptions.jsonc for the branch configuration, and ask @dotnet/dnceng if access or security questions arise. Done means the branch SHAs are unified, mirroring succeeds, and the issue can be closed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.