-
Notifications
You must be signed in to change notification settings - Fork 2
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
case(5): Rebase and merge #365
Conversation
Successfully created backport PR for |
This is an attempt to use korthout/backport-action#405 to backport this PR to backport-action/backport-action-test@case5-backport-target |
/backport |
My own /backport |
Git push to origin failed for case5-backport-target with exitcode 1 |
✅ Correctly fetched commits from origin:
✅ Correctly determined commits to cherry-pick using
✅ Correctly determined that target branch exists on upstream repository named
✅ Correctly switched to target branch from upstream repository:
❌ Failed to push because of permissions:
This makes sense, because the default |
Git push to origin failed for case5-backport-target with exitcode 1 |
Write access should now be provided using a token for the checkout action. Let's retry /backport |
Resource not accessible by integration |
This failed because the PR creation failed. Note we should clarify the error message. I've now added a token to the backport-action as well. Let's retry: /backport |
Git push to origin failed for case5-backport-target with exitcode 1 |
It failed because the target branch was already pushed to it. Note that we should gracefully handle this case in the future or clarify the error message. The target branch is now removed. Let's retry /backport |
Successfully created backport PR for |
Git push to origin failed for case5-backport-target with exitcode 1 |
That worked. Let's retry with a different PAT. /backport |
Successfully created backport PR for |
Git push to origin failed for case5-backport-target with exitcode 1 |
Adds some changed lines