GITHUB_TOKEN permissions used by this action

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.
```yaml
name: Create comment # babel/actions/create-comment
github-token:
action-input:
input: token
is-default: false
permissions:
issues: write
issues-reason: to create issue comment

```
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](https://github.com/ossf/scorecard). Scorecards recommend using https://github.com/step-security/secure-workflows so developers can fix this issue in an easier manner.

Review the `babel/actions/create-comment` action and its `token` input, then compare its GitHub token usage with the listed `issues: write` permission. If the knowledge-base entry is inaccurate or the action's permissions have changed, report the discrepancy at the linked secure-workflows issue tracker; otherwise, no repository change is indicated.

Written by the indexing model from the issue text.