You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current process will store someone's personal token (gh_token) and keep "carrying it"/using it everywhere (including pipeline) ad vitam aeternam.
Github Actions provides the (less fine-grained) token GITHUB_TOKEN. Any particular reasons to not use that one instead?
The way I see it the personal token can be fine-tuned, re. permissions, as needed and the GITHUB_TOKEN is either permissive or not.
Is that the only reason, to have greater control over the permissions of the token?
Terraform Resources
No response
Detailed design
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
TL;DR
Current process will store someone's personal token (
gh_token
) and keep "carrying it"/using it everywhere (including pipeline) ad vitam aeternam.Github Actions provides the (less fine-grained) token GITHUB_TOKEN. Any particular reasons to not use that one instead?
The way I see it the personal token can be fine-tuned, re. permissions, as needed and the GITHUB_TOKEN is either permissive or not.
Is that the only reason, to have greater control over the permissions of the token?
Terraform Resources
No response
Detailed design
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: