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
It is unnecessary to create a personal access token when deploying to GH actions
Proposed solution
I recently learned that secrets.GITHUB_TOKEN is accessible, negating the need to create a personal access token, simplifying several steps + removing potential security issues that come with PATs.
This commit demonstrates my repository works when my previous secrets.TOKEN (which was manually set in secrets) is replaced by secrets.GITHUB_TOKEN, which is automatically set by actions. Fixing this documentation would necessitate removing a few sections regarding PATs.
The text was updated successfully, but these errors were encountered:
Documentation issue
Summary
It is unnecessary to create a personal access token when deploying to GH actions
Proposed solution
I recently learned that
secrets.GITHUB_TOKEN
is accessible, negating the need to create a personal access token, simplifying several steps + removing potential security issues that come with PATs.This commit demonstrates my repository works when my previous
secrets.TOKEN
(which was manually set in secrets) is replaced bysecrets.GITHUB_TOKEN
, which is automatically set by actions. Fixing this documentation would necessitate removing a few sections regarding PATs.The text was updated successfully, but these errors were encountered: