Skip to content

(Reusable) Workflows & GITHUB_TOKEN: advice to use PAT in docs? #21068

Discussion options

You must be logged in to vote

The main reasons I'm aware of:

  • Accessing a private repository other than the one running the workflow. The GITHUB_TOKEN is scoped to the repository, so it can't do that.
  • Making events caused by the workflow (e.g. a push to the repository) trigger additional workflows. Activities authorized with the GITHUB_TOKEN never do that to avoid unintentional recursive runs.

From a security point of view it's certainly good to carefully consider whether those are really necessary. 🙂

Replies: 2 comments 3 replies

Comment options

You must be logged in to vote
3 replies
@Adminyoungmarsnet
Comment options

@abhinandpn

This comment was marked as off-topic.

@dangthanhvinh003
Comment options

Answer selected by ringods

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Actions Build, test, and automate your deployment pipeline with world-class CI/CD Enterprise Discussions related to GitHub Enterprise Cloud and Enterprise Server Product Feedback Enterprise Admin Topics specifically related to GitHub Enterprise administration
5 participants