We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
staging
As expected, secrets are not passed to the runner when the PR is coming from a fork.
The difference can be seen here:
master
So we can only run the CI build when merging from local branches.
I am not a devops expert, but here are my suggestions on how to setup branches to streamline pull requests.
We could
main
We must
This would make it possible to setup different workflows for PRs and release / integration tests
The text was updated successfully, but these errors were encountered:
The branches are renamed and protected.
Sorry, something went wrong.
mmahut
No branches or pull requests
Description
As expected, secrets are not passed to the runner when the PR is coming from a fork.
The difference can be seen here:
master
.So we can only run the CI build when merging from local branches.
I am not a devops expert, but here are my suggestions on how to setup branches to streamline pull requests.
We could
master
tostaging
(keep as default)main
(not default)main
main
#11We must
main
andstaging
by pull request reviews and status checksmain
#10This would make it possible to setup different workflows for PRs and release / integration tests
The text was updated successfully, but these errors were encountered: