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

[backport v3.0-branch] backport of #52519 failed #52543

Closed
zephyrbot opened this issue Nov 25, 2022 · 2 comments
Closed

[backport v3.0-branch] backport of #52519 failed #52543

zephyrbot opened this issue Nov 25, 2022 · 2 comments
Assignees
Labels
Backport Backport PR and backport failure issues Stale

Comments

@zephyrbot
Copy link
Collaborator

This issue was created automatically because the backport of #52519 to v3.0-branch failed.

The backport to v3.0-branch failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v3.0-branch v3.0-branch
# Navigate to the new working tree
cd .worktrees/backport-v3.0-branch
# Create a new branch
git switch --create backport-52519-to-v3.0-branch
# Cherry-pick the merged commits of this pull request and resolve the conflicts
git cherry-pick -x 027b79ecc4f71d36dbd89b9e0fb1dab7d096f0f7~4..027b79ecc4f71d36dbd89b9e0fb1dab7d096f0f7
# Push it to GitHub
git push --set-upstream origin backport-52519-to-v3.0-branch
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v3.0-branch

Then, create a pull request where the base branch is v3.0-branch and the compare/head branch is backport-52519-to-v3.0-branch.

@zephyrbot zephyrbot added the Backport Backport PR and backport failure issues label Nov 25, 2022
@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

@github-actions github-actions bot added the Stale label Jan 25, 2023
@cfriedt cfriedt removed the Stale label Jan 26, 2023
@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

@github-actions github-actions bot added the Stale label Mar 28, 2023
@cfriedt cfriedt closed this as completed Apr 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backport Backport PR and backport failure issues Stale
Projects
None yet
Development

No branches or pull requests

2 participants