-
Notifications
You must be signed in to change notification settings - Fork 156
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
Update README.rst #2201
Update README.rst #2201
Conversation
This is a commit just to create a new PR and we have no intention of merging this.
closing this PR as it correctly asked me to approval before continuing |
re-opening to further discussion. Do we want the linting to run before we have to approve the rest or should we keep it as is where approval is needed for everything? |
in fact we could only have approval for those bits that need access to secrets? |
The best would be to have it only for the parts needing secrets. In that way an outsider can discover most problems without our involvement. I am a bit confused about how it actually will work. I thought it would not ask for approval if you were a developer within the team, but the comments above seems to indicate that it asked you to approve your own PR? |
All PRs run the same github action "CI Pust Testing". To allow the jobs within to access the secrets we use the on: In practise this means that before the tests (that define to run in the environment) will run we get an email and have to click an approve button. |
I have checked the box that says "allow administrators to bypass protection rules". I guess this means that it will still wait for approval but that we should be able to click a button somewhere to allow it to proceed without. At that point though it's easy enough to just click approve since unlike with the code reviews we can approve ourselves |
I believe this can just be closed. Reopen if required. |
This is a commit just to create a new PR and we have no intention of merging this.