Skip to content

Recommend GitHub App authentication in the ARC quickstart - #45762

Open
sushant-me wants to merge 1 commit into
github:mainfrom
sushant-me:arc-quickstart-authentication-guidance
Open

Recommend GitHub App authentication in the ARC quickstart#45762
sushant-me wants to merge 1 commit into
github:mainfrom
sushant-me:arc-quickstart-authentication-guidance

Conversation

@sushant-me

Copy link
Copy Markdown

Why

The ARC quickstart currently instructs readers to generate a legacy personal access token (classic) as the default way to authenticate ARC to GitHub. For repository and organization runners, GitHub recommends authenticating with a GitHub App instead; a personal access token (classic) is only required for runners at the enterprise level.

What changed

  • The authentication step in the quickstart now points readers to the existing authentication guidance and recommends a GitHub App for repository and organization runners, while noting that a personal access token (classic) is required for enterprise-level runners.
  • Added a note near the PAT-based example clarifying that readers using a GitHub App should configure \githubConfigSecret\ with the app credentials (\github_app_id, \github_app_installation_id, and \github_app_private_key) instead of \github_token.

Verification

  • Anchor references in the updated links match existing section headings in the authentication guide.
  • No content was removed from the PAT-based example, which remains valid (and required) for enterprise-level configurations.

Closes #37288

@github-actions

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
actions/tutorials/use-actions-runner-controller/get-started.md fpt
ghec
ghes@ 3.22 3.21 3.20 3.19 3.18 3.17
fpt
ghec
ghes@ 3.22 3.21 3.20 3.19 3.18 3.17

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Sep 6, 2026
@subatoi subatoi closed this Sep 6, 2026
@subatoi subatoi reopened this Sep 6, 2026
@subatoi

subatoi commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Reopening—closed in error, apologies.

@subatoi subatoi added content This issue or pull request belongs to the Docs Content team and removed triage Do not begin working on this issue until triaged by the team labels Sep 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content This issue or pull request belongs to the Docs Content team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"Quickstart for Actions Runner Controller" recommends using a legacy user PAT for setting up ARC, which is poor practice

2 participants