-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Failing on private repositories because branch already exists. #277
Comments
Could you try to create a repository secret for a personal access token with the |
I use the search API to find out if there is an open pull request for the existing branch. There might be another way to achieve this, maybe using the GraphQL API, but I'm not sure |
I think this was due to the missing auth header in the search request (as present in other requests). PR opened: #282 |
The fix for #245 now works great for public repositories, but remains broken for private ones. When version 1.3.1 released, my builds continued to fail as before (so this isn't a regression), but now they fail because it seems like the GitHub token isn't enough for a private repo to be searched, which gives the error log dumped below. I confirmed it's the same issue because once I merge in the open PR it still fails, but once I delete the branch (which for my repo is configured to be called "auto-generated-changes") the workflow begins to pass again.
Any idea how I could resolve this? Are there more specific credentials I could pass in to allow the flow to succeed?
My config:
Raw logs:
The text was updated successfully, but these errors were encountered: