Repository navigation
Specify default permissions for pr-instructions.yml and wr-pr-instructions.yml #8589
Description
Prerequisites
- Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
- You have already read our How to Contribute to Hack for LA Guide.
Overview
We need to update the default permissions for the GitHub workflow specified in pr-instructions.yml and wr-pr-instructions.yml, so that it does not have more permissions than it needs.
Details
To align with GitHub security best practices, we want to specify the minimum required permissions for each workflow via a top-level permissions: block to ensure that workflows only have the access they need by default.
Every GitHub Actions workflow automatically receives a GITHUB_TOKEN with a set of default repository permissions defined in the repo settings which may result in the workflow having more permissions than it needs to complete its job. By explicitly defining minimum default permissions at the workflow level, we can ensure that workflow has only the permissions it needs. Then if a job or step requires more access, those permissions can be explicitly granted using job-level permissions statements or step-level tokens (PATs).
We performed an audit to identify the minimum top-level permissions required for each workflow. The goal of this and related issues is to verify that each workflow continues to function correctly with the explicitly defined permissions. This approach helps minimize unnecessary privileges and strengthen overall repository security.
For additional info, see issue #8178 and GitHub's recommendation for security best practice.
Action Items
Note that this issue involves testing GitHub Actions. See "Resources/Instructions" below for how to set up your personal environment for testing.
Refer to pr-instructions.yml:
- Review the file to understand how the workflow is triggered. This is specified near the top of the YML in the
on:section. - Near the top of the file immediately before the line
jobs:insert:permissions: contents: read pull-requests: read - Use clean formatting: make sure there is one line separation above and one below the permissions block.
Next, refer to wr-pr-instructions.yml:
- Review the file to understand how the workflow is triggered. This is specified near the top of the YML in the
on:section. - Near the top of the file immediately before the line
jobs:insert:permissions: contents: read actions: read issues: write - Use clean formatting: make sure there is one line separation above and one below the permissions block.
- If the workflows include line(s) similar to the following, you will need to change these to match your situation before the workflow will run correctly:
or
if: github.repository == 'hackforla/website'branches: - 'gh-pages' - Trigger the workflow to confirm whether both run successfully with no further changes to the permissions. Note that the second workflow is triggered by completion of the first.
- If there are errors:
- Try to determine the nature of the error, and whether it is occurring due to a mismatched repo or branch name.
- If you cannot track down the error, consult with the team via Slack or the weekly meetings to report your findings and get additional direction.
- If there are no errors, submit the PR like usual. Include a link to your test log.
Resources/Instructions
- Refer to The "Hack for LA's GitHub Actions" Wiki guide needs additional explanation #6537 (comment), especially Tips 6, 7, and 8, if you have not already created you personal environment for testing.
- How to Test GitHub Actions
- Additional Notes for GitHub Actions
- Tokens, Secrets, Scopes, & Permissions
Activity
[-]Specify default permissions for `pr-instructions.yml`[/-][+]Specify default permissions for `pr-instructions.yml` and `wr-pr-instructions.yml`[/+]13 remaining items
HackforLABot commentedon Sep 28, 2026
yielderdev commentedon Sep 28, 2026
ETA Update: 10-12-EOD. Getting merges & issue reviews done first
hfla-graphql-app commentedon Oct 16, 2026
yielderdev commentedon Oct 19, 2026
Posting new comment with updated ETA. Beginning work this a week after other tasks via merge team got added to top of my queue.
Availability: Tuesday 10-20-2026 12pm-2pm, 5pm-7pm, Thursday 10-22-26 2pm-5pm + evening, and intermittently throughout week.
hfla-graphql-app commentedon Oct 30, 2026
Hello @yielderdev-
Please add an update using the below template (even if you have a pull request). Afterwards, remove
the
status: To Update!label and add thestatus: Updatedlabel.If you need help, be sure to either: 1) place your issue in the "Questions / In Review" status-column of the
Project Board and ask for help at your next meeting; 2) put a
status: Help Wantedlabel on your issueand pull request; or 3) put up a request for assistance on the team's hfla-site Slack channel.
Please note that including your questions in the issue comments- along with screenshots, if applicable-
will help us to help you. Here and here are examples of well-formed questions.
You are receiving this comment because your last update was before 10/22/2026, 11:50 PM PDT PST.
hfla-graphql-app commentedon Nov 6, 2026
Hello @yielderdev-
Please add an update using the below template (even if you have a pull request). Afterwards, remove
the
status: 2 Weeks Inactivelabel and add thestatus: Updatedlabel.If you need help, be sure to either: 1) place your issue in the "Questions / In Review" status-column of the
Project Board and ask for help at your next meeting; 2) put a
status: Help Wantedlabel on your issueand pull request; or 3) put up a request for assistance on the team's hfla-site Slack channel.
Please note that including your questions in the issue comments- along with screenshots, if applicable-
will help us to help you. Here and here are examples of well-formed questions.
You are receiving this comment because your last update was before 10/23/2026, 12:00 AM PDT PST.