Current state
MindRail is public and GitHub Free rulesets are available. The permanent Quality workflow is healthy.
Observed required check on the current PR head:
- check name:
quality
- GitHub App/source: GitHub Actions
- reconciliation run
33224006475: SUCCESS
The GitHub connector used by the maintainer's automation can read rulesets but does not expose create/update ruleset writes, so this repository-level control requires a one-time GitHub Settings action.
Required ruleset
Create an Active branch ruleset targeting the default branch (main) with:
- Require a pull request before merging.
- Do not require approving reviewers yet; MindRail currently has one maintainer.
- Require status checks to pass before merging.
- Required check:
quality.
- Expected source: GitHub Actions if GitHub offers the source selector.
- Leave “Require branches to be up to date before merging” disabled initially to avoid duplicate CI runs for a single-maintainer repository; revisit when concurrent contribution volume justifies strict mode.
- Block force pushes.
- Restrict deletions / prevent deletion of the targeted branch.
- Require conversation resolution before merging if that rule is offered in the current UI.
- No broad bypass actors. Add an admin bypass only if a deliberate recovery path is needed.
GitHub UI path: Settings → Rules → Rulesets → New ruleset → New branch ruleset.
Verification after creation
- API
/repos/tim8es/mindRail/rulesets returns the active ruleset.
- A test PR with a deliberately failing or missing
quality check cannot merge.
- A green PR can merge through the normal PR path.
docs/CURRENT_STATE.md and .github/PUBLIC_RELEASE_CHECKLIST.md are reconciled with observed enforcement.
Done when
The ruleset is active and the blocking behavior is demonstrated, not merely configured.
Current state
MindRail is public and GitHub Free rulesets are available. The permanent
Qualityworkflow is healthy.Observed required check on the current PR head:
quality33224006475: SUCCESSThe GitHub connector used by the maintainer's automation can read rulesets but does not expose create/update ruleset writes, so this repository-level control requires a one-time GitHub Settings action.
Required ruleset
Create an Active branch ruleset targeting the default branch (
main) with:quality.GitHub UI path: Settings → Rules → Rulesets → New ruleset → New branch ruleset.
Verification after creation
/repos/tim8es/mindRail/rulesetsreturns the active ruleset.qualitycheck cannot merge.docs/CURRENT_STATE.mdand.github/PUBLIC_RELEASE_CHECKLIST.mdare reconciled with observed enforcement.Done when
The ruleset is active and the blocking behavior is demonstrated, not merely configured.