You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During VMR codeflows, when there are conflict in repo sources, the PR branch and the target branch will require the user to resolve the conflict.
However, since we won't be able to merge target branch into the PR branch automatically, there will also be conflicts in the version files.
This means that the dev will need to resolve these as well.
There is a danger that the dev will resolve the version files incorrectly and might break the code flow. For this reason, the PR will contain a comment which will guide the dev through the conflict resolution.
The instructions will contain steps to use darc to resolve the conflicts properly. Darc will resolve the version files conflict and let the user resolve the source file conflicts.
Goal
We want to add a new darc command darc vmr resolve-conflict. This command will:
It will be executed from the cloned repo
It will accept following options:
--pr [ID]
-s|--strategy pr|target|manual - a conflict resolution strategy (see modes below)
Work in 2 modes:
Manual resolution - Resolve version files only (and let the user finalize the conflict resolution)
Auto-resolution - Resolve the source code changes (accept the PR branch or the target branch versions)
It will do the following:
Read remotes from the git repo it runs from
Find the PR in the remotes (either AzDO or GitHub)
Query PCS to get the updates the PR contains (this is possible already via the new PR endpoint)
Checkout the PR branch and start the merge of the target branch
Apply the resolution strategy
For manual resolution, this will resolve the version files conflicts (just like the service would do it) and then stop - give user the next steps - resolve conflicts, commit, push
Context
During VMR codeflows, when there are conflict in repo sources, the PR branch and the target branch will require the user to resolve the conflict.
However, since we won't be able to merge target branch into the PR branch automatically, there will also be conflicts in the version files.
This means that the dev will need to resolve these as well.
There is a danger that the dev will resolve the version files incorrectly and might break the code flow. For this reason, the PR will contain a comment which will guide the dev through the conflict resolution.
The instructions will contain steps to use
darc
to resolve the conflicts properly. Darc will resolve the version files conflict and let the user resolve the source file conflicts.Goal
We want to add a new darc command
darc vmr resolve-conflict
. This command will:--pr [ID]
-s|--strategy pr|target|manual
- a conflict resolution strategy (see modes below)The text was updated successfully, but these errors were encountered: