-
-
Notifications
You must be signed in to change notification settings - Fork 438
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
PR branch is not ahead of base 'main' and will not be created #3575
Comments
Hi @petlitskiy I'm not sure I understand your use case. If you show me your workflow(s) I might be able to help.
The only retry that occurs is for retryable errors from the API. There's no other retry options. |
`
##[group]Checking the base repository state testing senario is created a fresh repo. added the workflow. created several test branches add random crap and sent it off to see if it create a pr request it says the same thing. branch is not ahead. |
@gomeology I need to see the whole workflow, not just the action step. It matters what triggers the workflow and what changes you are making before the action runs. |
@peter-evans ok so maybe i misunderstood what this is doing. when looking at your example i have to add date+%S > report.txt. is this because it needs to be modified from within the workflow? Im new to this so bear with me. But I want to create a PR whenever a new push is made. I now added your date command line and I am getting "::error::Not found.%0A". im guessing this is because the token is not getting to where it needs to be. but here is the workflow. Can you also answer if i need the 'make changes to pull request' for this to work? ` on: jobs:
` |
Subject of the issue
Action creates PR from repo A to repo B. And (very rarely) we are faced with
After we have renewed with new commits - we can recreate the target PR (refreshed with new commits as well).
Looks like another PR succeeded and merged to the
main
branch on repo B at the moment of creation of the first mentioned PR (from repo A).Steps to reproduce
Is there any option on this action that provides retries of PR creation for some time with some pause periods?
The text was updated successfully, but these errors were encountered: