security(workflow): Set permissions for GitHub actions

[naveensrinivasan]

• Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions

https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs

Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests

Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much.

Signed-off-by: naveensrinivasan [email protected]

[davorpa]

With #6202 permissions needs be extended to read.

I also have in mind autotag PR with linter error label depend on linter status. How it would be?

[naveensrinivasan]

With #6202 permissions needs be extended to read.

Can that be a separate one?

I also have in mind autotag PR with linter error label depend on linter status. How it would be?

That is probably within your code in JS. I couldn't figure that out. You can set permissions specific to the Job using this https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idpermissions

permissions:
      issues: write

[davorpa]

Thanks for your all support @naveensrinivasan!

Can that be a separate one?

Of course. It only was linked to take in mind this changes.

Let's wait what tell us other members with a bit more experience with GH actions. @SethFalco @borgified is this PR suitable and usefull?

[davorpa]

LGTM after reading the documentation and some other @SethFalco 's messages about Actions security

• ci(workflow): post build result as comment #5564 (comment)
• build(fpb-lint): linting errors as PR comments, resolved #4416 #6914 (comment)

It ensures same behavior across forks/origin with zero config