Closed edsml-yz1921 closed 2 years ago
Your workflow will be unaffected by a regenerated token, as you do not use a custom GitHub token in your workflow.
Actions issues a new GITHUB_TOKEN
at the start of each workflow run, which can be used by steps to authenticate with the GitHub API. (See docs)
The actions/checkout
-Action uses the default GITHUB_TOKEN
to authenticate the git repository.
As long as you do not override the token
argument for the actions/checkout
-Action, you're good to go.
Version of the Action
v4
Describe the bug GitHub noticed that my personal access token is going to expire. If I regenerate a new and equivalent token, will it affect the original functionality of the workflow?
Expected behavior The workflow execute the python files to generate a new txt file and the action commits and pushes the new file to the repo. After updating the personal access token, new token does not affect the expected behavior.
Used Workflow