Open gilgongo opened 3 years ago
Hi @gilgongo
I developed the main code of this action more than a years ago and seems the way the action runs with the secrets changed a bit ever since. Now seems you do not need to generate a Personal Access Token and use the statement GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
in your workflow file for personal repositories projects (projects that are in your personal repositories), though my action does not reflect this just yet. In any case for projects that belong to an organisation (not personal), you need to generate a Personal Access Token with org
permissions (see #58) and use it in your workflow file MY_GITHUB_TOKEN: ${{ secrets.MY_GITHUB_TOKEN }}
where MY_GITHUB_TOKEN
is the name of the newly generated token.
Hope that is clear.
I'm planning to remove the secrets.GITHUB_TOKEN
from the action for personal projects.
Cheers, Sergio
Hi - Just a minor thing, but When it says:
"Generate a token from the Organisation settings or User Settings "
It would be clearer as:
"Generate a secret from the Organisation settings or User Settings "
There is no item for "tokens" in the GitHub menu (nor do they refer to creating tokens in their documentation).
EDIT: But wait... what's this https://github.com/srggrs/assign-one-project-github-action/issues/61 ?