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
Switch to automatically set up GITHUB_TOKEN #66
Conversation
Not sure how the checks here work in a PR, and whose secrets they inherit? |
Just to confirm things should work, here is my
The only commit in-between, with only changes to the And AFAIK I have no secret set up for this repo. |
Thanks so much for the PR @js2264 , this has been a point of confusion for me for a long time. Ideally I'd like to get rid of any additional setup steps outside of the Also thanks for being an early adopter of All the best, |
Oh also, I'm going to try to switch this PR to the dev branch, so that we can play around with these changes without affecting other users just yet. The dev branch will then be run using this workflow: |
Awesome work @js2264 , everything is now merged and working great. This goes a long way towards making Thanks again, |
Update docs to reflect PR #66
Currently the
rworkflows.yml
requires a specific "PAT_GITHUB" secret to be set up in each repo using the GHA.However, GitHub automatically sets up
{{ secrets.GITHUB_TOKEN }}
for any GHA job, without needing to set it up manually, so this could be used instead of a manually set up "PAT_GITHUB".This requires adding
permissions
set forcontents: write
for any job relying on{{ secrets.GITHUB_TOKEN }}
, otherwise JamesIves deploy GHA won't work (see here: https://github.com/JamesIves/github-pages-deploy-action#:~:text=If%20you%20do,permissions%20it%20needs.)More here: https://docs.github.com/en/actions/security-guides/automatic-token-authentication