Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjust backport PR branch name #4606

Merged
merged 1 commit into from
Jan 10, 2025

Conversation

Youssef1313
Copy link
Member

No description provided.

@Youssef1313 Youssef1313 merged commit c9f965b into microsoft:main Jan 10, 2025
1 check passed
@Youssef1313 Youssef1313 deleted the backport-branch-name branch January 10, 2025 08:18
@Youssef1313
Copy link
Member Author

/backport to rel/3.7

Copy link
Contributor

Started backporting to rel/3.7: https://github.com/microsoft/testfx/actions/runs/12705785809

Copy link
Contributor

@Youssef1313 backporting to rel/3.7 failed, the patch most likely resulted in conflicts:

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Applying: Adjust backport PR branch name
Using index info to reconstruct a base tree...
A	.github/workflows/backport-base.yml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): .github/workflows/backport-base.yml deleted in HEAD and modified in Adjust backport PR branch name. Version Adjust backport PR branch name of .github/workflows/backport-base.yml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Adjust backport PR branch name
Error: The process '/usr/bin/git' failed with exit code 128

NOTE: A PR will be created, but needs to be revised manually!**

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant