Add Ruleset support#51
Open
maclarel wants to merge 2 commits into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
GitHound currently only pulls classic branch protection rules which results in blindspots in data and can result in branches being incorrectly noted as being unprotected.
This change introduces support for Rulesets - retrieving them through GraphQL, identifying their source (repo vs org), enforcement status (active vs evaluate), and correcting the "protected" state of a given branch to include coverage from protection rules.
No schema changes are required to support this, and similarly this should not introduce any breaking changes. Imports on top of historical data pulls completes (in my testing) without error.
This PR was heavily AI-assisted, but is working as expected against live environments in my testing so far 🤞