-
-
Notifications
You must be signed in to change notification settings - Fork 439
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
Disable force pushes into PR branch #664
Comments
Hi @onedr0p This is fundamental to how the action is designed to work and there is no option to disable it at the moment. It makes sure pull request branches up-to-date every time the action is run. For example, if the commit from the pull request was cherry-picked to the base branch then the next run of the action would detect that there is no more diff and close the pull request. Is there a reason you don't want it to update? If you really don't want it to update then what that effectively means is that you don't want the action to run. So one option you could try is adding a step to detect if the pull request branch exists and exit the workflow if it does. |
The files that are being modified in my workflow are files that would never be changed by a human, so there's no issue of a merge conflict happening. Having the PR be up-to-date isn't really needed and I get spammed with Github notifications everytime it happens.
This is good work-around and will implement it, but would be awesome if it was built into the action as well. Thanks! |
It appears as though github actions doesn't have a way to gracefully exit a workflow based on a condition or not, so the only way for that work-around is have the workflow fail when the branch exists which is not ideal. https://stackoverflow.com/questions/57903836/how-to-fail-a-job-in-github-actions |
Fairly sure you can just skip steps that you don't want to run without it failing the workflow. Closing this issue, but feel free to continue the conversation. |
Subject of the issue
I have a schedule set up to open a PR when it notices a new version of Flux2
I notice that it keeps force pushing master into this branch when changes are made in master, is there anyway to disable this behavior?
Steps to reproduce
The text was updated successfully, but these errors were encountered: