Skip to content
New issue

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

Why use personal token vs. GITHUB_TOKEN? #1274

Open
lpezet opened this issue Jun 23, 2024 · 1 comment
Open

Why use personal token vs. GITHUB_TOKEN? #1274

lpezet opened this issue Jun 23, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@lpezet
Copy link
Contributor

lpezet commented Jun 23, 2024

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

@lpezet lpezet added the enhancement New feature or request label Jun 23, 2024
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Aug 22, 2024
@eeaton eeaton removed the Stale label Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants