follow up to: 2d5eced
Our idea is to add separate permission_* parameters for each permission supported by GitHub Apps:
https://docs.github.com/en/rest/overview/permissions-required-for-github-apps
The permission_* keys can be generated based off https://github.com/octokit/app-permissions. Each time a new version of @octokit/app-permissions is released, the action.yml could be updated, in order to keep permissions always up-to-date. The README.md should be updated as well to make sure the documentation is up-to-date as well. Most permissions can be set to read or write, some can also be set to admin.
Having separate permissions has the benefit of code intelligence and errors shown directly on GitHub when an unknown permission is set due to a typo.
follow up to: 2d5eced
Our idea is to add separate
permission_*parameters for each permission supported by GitHub Apps:https://docs.github.com/en/rest/overview/permissions-required-for-github-apps
The
permission_*keys can be generated based off https://github.com/octokit/app-permissions. Each time a new version of@octokit/app-permissionsis released, theaction.ymlcould be updated, in order to keep permissions always up-to-date. TheREADME.mdshould be updated as well to make sure the documentation is up-to-date as well. Most permissions can be set toreadorwrite, some can also be set toadmin.Having separate permissions has the benefit of code intelligence and errors shown directly on GitHub when an unknown permission is set due to a typo.