Require CI checks for LibreSign .github - #5
Merged
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
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.
Summary
Require the repository's CI checks before changes can be merged into the default branch, without adding these repository-specific requirements to the shared ruleset used by other projects.
Architecture
Ruleset synchronization now composes policies in two layers:
The existing Nextcloud app behavior remains part of the base ruleset because it controls direct translation pushes to both the default branch and maintained
stable*branches.LibreSign/.githubnow receives a second ruleset that applies only to its default branch and requires:Ruleset sync behavior and policyShellCheckactionlintzizmorThis keeps repository-specific CI requirements isolated from the common branch policy.
Testing
The Bats suite now verifies policy composition, ensures ordinary repositories receive only the base ruleset, confirms the repository-specific ruleset does not trigger Nextcloud detection, and validates all required status checks.