-
Notifications
You must be signed in to change notification settings - Fork 60
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
Whatever I do i get a "branch is invalid or doesn't exist" #484
Comments
Hi there, What version of backport are you using? Try |
I think I found the issue. You are trying to backport a commit from the branch The error message is currently misleading. i'll add a fix to improve that. Btw. I tried figuring out on which branch the commit lives, but it looks like it's an orphan: |
The branch existed locally in my local repo, as the commit is in a private fork, so I couldn't really point at any upstream PR number. So I started with I'd really love some |
There are logs in
|
The way the backport tool works, is that it clones the repository into a temporary folder, and performans the git operations there. The commit you want to backport therefore needs to be available in the upstream repository - not just locally. |
Is there any way to backport a PR/commit from a private fork to a public upstream one? Is it something that could be supported? |
I don't think so. |
I thought that |
I'm trying to use
backport
locally for convenient backporting, but no matter what access token I give it I'm hitting:Is there a
-v
flag or something where I could look at what is going on under the hood?The text was updated successfully, but these errors were encountered: