Scripts for role and membership validation #110
Merged
Conversation
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
joshjohanning
approved these changes
Aug 13, 2025
Owner
joshjohanning
left a comment
joshjohanning
left a comment
There was a problem hiding this comment.
LGTM! ✨ 🎉 Only major thing I changed was check-org-team-membership to check-organization-team-membership to satisfy the linting.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
New scripts for role and membership checks
check-enterprise-owner.shto verify if a user is an enterprise admin using the GitHub GraphQL API, including pagination support and detailed error handling.check-enterprise-team-membership.shto check if a user is a member of an enterprise team (private preview feature) using the REST API, with HTTP status code handling.check-org-team-membership.shto check if a user is a member of a specific team in an organization via the REST API, requiring theread:orgscope.check-repository-admin.shto determine if a user is a collaborator in a repository and whether they have admin access, with permission level checks.