docs: document PAT-based GitHub repository connection - #501
Merged
Conversation
Replace the disabled OAuth flow (kept commented out in case it's re-enabled) with steps for connecting a GitHub repo via a classic or fine-grained personal access token, including a token overview and updated screenshots. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…checker to not ignore those blocks
…m in the wordlist The heading was the only place these identifiers appeared unbackticked, so the spellchecker read them as prose while ignoring the ~20 other occurrences already inside code spans and json fences. Backticking matches the convention used throughout the rest of the file and avoids adding camelCase tokens to the wordlist, where they would mask future typos of those field names. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace the disabled OAuth flow (kept commented out in case it's re-enabled) with steps for connecting a GitHub repo via a classic or fine-grained personal access token, including a token overview and updated screenshots.