We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
You may have an issue in your README.md file about workarounds for permissions issues with the standard GITHUB_TOKEN:
Private repositories In some cases you may want to do add this functionality for a private repository or one you do not have admin rights to. You may get an error like: GraphqlError: Resource not accessible by integration When this happens you will need to: Create a personal access token Create a secret containing the personal access token, call it GITHUB_TOKEN Change the repo-token in the workflow .yml to reference your new token name: repo-token: ${{ secrets.GITHUB_TOKEN }} With certain organisations there may be SAML enforcement. This means you will need to Enable SSO when you create the personal access token. GraphqlError: Resource protected by organization SAML enforcement. You must grant your personal token access to this organization
In some cases you may want to do add this functionality for a private repository or one you do not have admin rights to. You may get an error like:
GraphqlError: Resource not accessible by integration
When this happens you will need to:
GITHUB_TOKEN
repo-token
.yml
repo-token: ${{ secrets.GITHUB_TOKEN }}
With certain organisations there may be SAML enforcement. This means you will need to Enable SSO when you create the personal access token.
Enable SSO
GraphqlError: Resource protected by organization SAML enforcement. You must grant your personal token access to this organization
If a user tries to create a secret called GITHUB_TOKEN they will be denied as it is a reserved keyword. I would suggest MY_GITHUB_TOKEN instead. 💜
MY_GITHUB_TOKEN
The text was updated successfully, but these errors were encountered:
GH_TOKEN
Thanks @affrae this is resolved in the latest version https://github.com/alex-page/github-project-automation-plus/releases/tag/v0.2.3
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
You may have an issue in your README.md file about workarounds for permissions issues with the standard GITHUB_TOKEN:
If a user tries to create a secret called
GITHUB_TOKEN
they will be denied as it is a reserved keyword. I would suggestMY_GITHUB_TOKEN
instead. 💜The text was updated successfully, but these errors were encountered: