Dev

[smalho01]

Describe your changes

Please include a summary of the changes and the related issue/task. Please also include relevant motivation and context. List any dependencies that are required for this change, including links to other pull requests/branches in other repositories if applicable.

Issue ticket number and Jira link

Please include the Jira Ticket Number and Link for this issue/task.

Checklist before requesting a review

• I have performed a self-review of my code
• Ensure the target / base branch for any feature PR is set to dev not main (the only exception to this is releases from dev and hotfix branches)

Checklist for conducting a review

• Review the code changes and make sure they all make sense and are necessary.
• Pull the PR branch locally and test by running through workflow and making sure everything works as it is supposed to.

Workflow

Owner of the Pull Request will be responsible for merge after all requirements are met, including approval from at least one reviewer. Additional changes made after a review will dismiss any approvals and require re-review of the additional updates. Auto merging can be enabled below if additional changes are likely not to be needed. The bot will auto assign reviewers to your Pull Request for you.

To fix the issue, we will add a permissions block at the root of the workflow file. This block will define the minimal permissions required for the workflow to function. Since the workflow primarily involves linting, testing, and installing dependencies, it only needs contents: read permissions. This ensures that the GITHUB_TOKEN has the least privilege necessary to perform these tasks.

The permissions block will be added immediately after the name and on keys in the workflow file.

---

To fix the issue, we need to add a permissions block to the workflow file. This block should specify the minimal permissions required for the workflow to function correctly. Since the workflow only performs linting, testing, and formatting tasks, it does not require write access to the repository. Therefore, the permissions block should set contents: read at the root level of the workflow to apply to all jobs. This ensures that the GITHUB_TOKEN has only read access to the repository contents.

To fix the issue, we will add a permissions block at the root of the workflow file. This block will define the minimal permissions required for the workflow. Since the workflow primarily performs linting and testing tasks, it does not require write permissions. We will set contents: read as the permission, which is sufficient for accessing the repository's contents.

The permissions block will be added immediately after the name field at the top of the file. This ensures that the permissions apply to all jobs in the workflow unless overridden by a job-specific permissions block.

---

To fix the issue, we will add a permissions block to the root of the workflow file. This block will define the minimal permissions required for the workflow to function. Since the workflow primarily involves linting, testing, and installing dependencies, it only needs read access to the repository contents. We will set contents: read as the permission for the entire workflow.