Harden public branch protection baselines - #36
Merged
Conversation
Document and codify stricter PR and CI requirements so public-facing changes cannot bypass review or quality gates.
Add comprehensive ApiClient and M2M unit tests plus config-path branch tests, and wire pytest/CI to fail below 100% on the covered unit-test surface.
Install the package in editable mode for unit-test jobs so pytest-cov measures the checked-out sources and enforces the 100% gate correctly.
Set required approvals to zero and disable last-push approval in main/release protection rulesets, and document that repo write access must be limited to internal staff via role assignments.
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
mainandrelease/*Test plan