GITHUB_TOKEN permissions used by this action

[step-security-bot]

At https://github.com/step-security/secure-workflows we are building a knowledge-base (KB) of GITHUB_TOKEN permissions needed by different GitHub Actions. When developers try to set minimum token permissions for their workflows, they can use this knowledge-base instead of trying to research permissions needed by each GitHub Action they use.

Below you can see the KB of your GITHUB Action.

name: 'PR Welcome'
github-token:
  action-input:
    input: token
    is-default: true
  permissions:
    issues: write
    issues-reason: to create, update & react on issues #Checkout: https://github.com/actions-cool/pr-welcome/blob/main/src/main.js#L171
    pull-requests: write
    pull-requests-reason: to request reviewer #Checkout: https://github.com/actions-cool/pr-welcome/blob/main/src/main.js#L147
    contents: read
    contents-reason: to get collaborator permission level #Checkout: https://github.com/actions-cool/pr-welcome/blob/main/src/main.js#L57

    
#Fixes #548

If you think this information is not accurate, or if in the future your GitHub Action starts using a different set of permissions, please create an issue at https://github.com/step-security/secure-workflows/issues to let us know.

This issue is automatically created by our analysis bot, feel free to close after reading :)

References:

GitHub asks users to define workflow permissions, see https://github.blog/changelog/2021-04-20-github-actions-control-permissions-for-github_token/ and https://docs.github.com/en/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token for securing GitHub workflows against supply-chain attacks.

Setting minimum token permissions is also checked for by Open Source Security Foundation (OpenSSF) Scorecards. Scorecards recommend using https://github.com/step-security/secure-workflows so developers can fix this issue in an easier manner.