Markdown compatibility1 detected · 1 enabled · mkdocs docs
Docs project
mkdocs · Generate A GitHub PAT · 28 section pages
Generate A GitHub PAT
- HomeREADME.md
- Getting starteddocs/getting-started.md
- Core conceptsdocs/core-concepts.md
- Demo walkthroughdocs/demo-walkthrough.md
- Review pull requestsdocs/review-pull-requests.md
- Review repository branchesdocs/review-repository-branches.md
- Draft reviewsdocs/draft-reviews.md
- Brainstorming Reviewsdocs/brainstorming-reviews.md
- Live Preview Reviewsdocs/web-app-reviews.md
- Commentary Formsdocs/commentary-forms.md
- Review progressdocs/review-progress.md
- Review modesdocs/review-modes.md
- Workspacedocs/workspace.md
- Markdown renderingdocs/markdown-rendering.md
- Markdown extensionsdocs/markdown-extensions.md
- Static HTML reviewdocs/static-html-review.md
- Knowledge Braindocs/knowledge-brain.md
- Access and authenticationdocs/access-and-authentication.md
- Developer accessdocs/developer-access.md
- Generate a GitHub PATCurrent page
- Azure DevOpsdocs/azure-devops.md
- Commentary CLIdocs/commentary-cli.md
- Agent skillsdocs/agent-skills.md
- API and MCPdocs/api-and-mcp.md
- API referencedocs/api/reference.md
- MCP toolsdocs/api/mcp-tools.md
- Blogdocs/blog.md
- Troubleshooting and FAQdocs/troubleshooting-and-faq.md
Enabled
- MkDocsMkDocs rendering is enabled. MkDocs-specific syntax remains visible as ordinary Markdown when compatibility rendering is unavailable.
DocsGenerate A Github Pat
28 pages from docs configurationmkdocs
Generate A GitHub PAT
Use a GitHub personal access token only when Commentary's normal GitHub App sign-in is not available. For most users, Continue with GitHub is simpler and gives Commentary installation-aware access.
Prefer a fine-grained PAT instead of a classic token.
Create The Token
- Sign in to GitHub.
- Open
Settings. - Open
Developer settings. - Open
Personal access tokens, thenFine-grained tokens. - Click
Generate new token. - Give the token a clear name and choose an expiration date.
- Set the resource owner that owns the repository you want to review.
- Limit repository access to only the repository or repositories you need.
- Grant the minimum repository permissions for your task.
- Generate the token.
- Copy it immediately. GitHub will not show the full token again.
- In Commentary, click
Sign in. - Open
Use personal access token. - Paste the token and submit.
Repository Permissions
Use GitHub's fine-grained repository permissions:
- To view a repository in Commentary, grant
ContentswithRead-onlyaccess. - To view a pull request, grant
ContentswithRead-onlyaccess andPull requestswithRead-onlyaccess. - To comment on a pull request from Commentary, keep
ContentsasRead-onlyand grantPull requestswithRead and writeaccess.
Keep It Narrow
- Use fine-grained tokens.
- Limit the token to the smallest repository set that works.
- Set an expiration date.
- Revoke tokens you no longer need.
If Commentary says the token is accepted but the repository still fails, the token usually lacks a repository or permission GitHub requires for the attempted action.
GitHub Docs
- Managing personal access tokens: GitHub Docs
- Fine-grained PAT permissions reference: GitHub Docs