Add explicit permissions to test.yml workflow

[Copilot]

The test.yml workflow was missing explicit permissions configuration, which is a security best practice for GitHub Actions.

Changes:

• Added permissions: contents: read at workflow level in .github/workflows/test.yml

This is the minimum required permission for the workflow, which only checks out code, sets up Node.js, and runs npm commands. The publish.yml workflow already has explicit permissions at the job level.

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

permissions:
  contents: read

jobs:
  build:
    runs-on: ubuntu-latest

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/test.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 #336

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull Request Overview

This PR adds explicit permissions configuration to the test.yml GitHub Actions workflow, implementing the security best practice of defining minimal required permissions. The workflow previously relied on default permissions, which could grant more access than necessary.

• Added permissions: contents: read at the workflow level
• Follows the principle of least privilege by granting only the minimum permission needed for checking out code and running tests
• Aligns with existing security practices in the repository (the publish.yml workflow already has explicit permissions)

---

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