Repository navigation
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
abhijna
marked this pull request as draft
August 22, 2026 00:23
abhijna
marked this pull request as ready for review
August 28, 2026 18:29
armchairlinguist
requested changes
Aug 31, 2026
armchairlinguist
left a comment
Collaborator
There was a problem hiding this comment.
This definitely needs some refinement - while I've flagged a few things I noticed, I would highly recommend checking this with an SCM SME from the platform team.
…thub-pat-permissions
…rmissions' of github.com:semgrep/semgrep-docs into abhijna/tec-629-improve-documentation-for-github-pat-permissions
abhijna
commented
Sep 2, 2026
abhijna
left a comment
Collaborator
Author
There was a problem hiding this comment.
@armchairlinguist I checked with Zach and made changes accordingly. Summary:
- If you have both a PAT and an app configured, the app takes precedence.
- A PAT can actually be used instead of a private GitHub App for SMS!
- You do not need
Contents: Read and writefor Semgrep to leave PR comments. You only needPull requests: Read and write.
armchairlinguist
approved these changes
Sep 11, 2026
armchairlinguist
left a comment
Collaborator
There was a problem hiding this comment.
Mostly just minor comments, some of which are opinion-y rather than important :)
Co-authored-by: Alexis Grant <alexis@semgrep.com>
Co-authored-by: Alexis Grant <alexis@semgrep.com>
Co-authored-by: Alexis Grant <alexis@semgrep.com>
Co-authored-by: Alexis Grant <alexis@semgrep.com>
…ation-for-github-pat-permissions' Co-authored-by: Cursor <cursoragent@cursor.com>
…thub-pat-permissions
abhijna
deleted the
abhijna/tec-629-improve-documentation-for-github-pat-permissions
branch
September 14, 2026 18:14
This branch was successfully deployed
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.
This PR updates the GitHub permissions docs so PAT users (including orgs still on classic tokens) can see what scopes and roles they need.
Reorg
Review focus: Are the classic vs fine-grained scopes right for connection validation, and does the public/private App + PAT layout make sense?