"Quickstart for Actions Runner Controller" recommends using a legacy user PAT for setting up ARC, which is poor practice · github/docs#37288

(14 评论) (1 反应) (0 负责人)TypeScript (19,479 star) (67,056 fork)batch import

SME reviewedcontentgithub_actionshelp wanted

描述

Code of Conduct

I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://github.com/github/docs/blob/main/content/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/deploying-runner-scale-sets-with-actions-runner-controller.md

What part(s) of the article would you like to see updated?

Reading the helm values for the gha-runner-scale-set chart, the helm chart supports authenticating via github app, which is a more secure and production grade method of configuring ARC than using a user's personal access token.

The docs should be updated to nudge people towards the more proper way of doing things.

Additional information

I know github is trying to phase out classic PATs so it was unexpected to see official docs instructing to use a PAT, especially when other methods are supported.

贡献者指南

技术栈: github actionskubernetes
领域: documentation
议题类型: documentation
难度: 2
预计时间: 1-3 hours
活动状态: active
清晰度: clear
前置要求: Knowledge of GitHub ActionsUnderstanding of GitHub App vs PATBasic Markdown editing
新手友好度: 85
研究方向: Review the linked article file (content/actions/hosting your own runners/managing self hosted runners with actions runner controller/deploying runner scale sets with actions runner controller.md) and the 13 comments to identify sections recommending PAT usage. Propose changes to prefer GitHub App authentication, referencing the helm chart values that support it. Ensure alignment with GitHub's deprecation policy for classic PATs.