Add explicit permissions to pr.yml workflow

[Copilot]

The pr.yml workflow lacked explicit permissions definition, which is a security best practice for GitHub Actions.

Changes

• Added permissions: contents: read to the test job in .github/workflows/pr.yml

This grants only the minimum permission required for actions/checkout@v4 to read repository contents. The workflow performs no writes, deployments, or API operations that would require additional permissions.

jobs:
  test:
    runs-on: ubuntu-latest
    permissions:
      contents: read
    steps:
      - uses: actions/checkout@v4
      # ...

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• www.googleapis.com
  • Triggering command: node install.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Please define actions workflow permissions</issue_title>
<issue_description>## Workflow permissions improvement

There are 1 workflow file that are currently lacking explicit permissions

Affected Workflow Files

The following workflow files need permissions to be explicitly defined:

• .github/workflows/pr.yml

Request

Ensure permissions are explicitly defined. Below are Copilot prompts/instructions if you would like Copilot's assistance with addressing this.

GitHub Copilot Assignment Prompts and Context

Task: Add explicit permissions to GitHub Actions workflow files that are currently missing them.

Scope: Update the workflow files listed above to include appropriate permissions: blocks.

Analysis Methodology:

1. Gather Current State: Check if the workflow has any existing permissions defined
2. Inventory Workflow Actions:
   • Actions performed directly by the workflow
   • API calls made by the workflow
   • External actions included via uses: statements
3. Determine Required Permissions: Map each action to its minimum required permissions
4. Synthesize Minimal Permissions: Create permissions block with only necessary permissions

Requirements:

1. Add a permissions: block to each workflow file that doesn't have one
2. Start with contents: read as the minimum permission
3. Add additional permissions only if the workflow actually needs them based on the actions it performs
4. Place the permissions: block at the job level or workflow level as appropriate
5. Ensure the syntax is correct and follows YAML formatting
6. Maintain existing content formatting, including indentation and comments

Files to modify: See the list of affected workflow files above.

Acceptance criteria:

• All listed workflow files have explicit permissions defined
• Permissions follow the principle of least privilege
• YAML syntax is valid
• Workflows still function correctly after changes

Copilot Instructions:

Please create a pull request that adds appropriate permissions: blocks to each of the workflow files listed above. Analyze each workflow to determine the minimum permissions required based on the actions it performs, and add only those necessary permissions.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Please define actions workflow permissions #42

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull Request Overview

This PR adds explicit permissions to the pr.yml GitHub Actions workflow, implementing a security best practice by following the principle of least privilege. The change aligns with the existing pattern already established in the publish.yml workflow file.

• Added job-level permissions: contents: read to the test job
• Grants minimal permissions needed for the workflow's read-only operations (checkout, npm ci, lint, build, test)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.