docs(ci): harness-ci is a signal, not a hard ruleset gate (align with homelab-ops)#23
Merged
Conversation
… homelab-ops) Making harness-ci a required status check deadlocked the adr-assign numbering PR (GITHUB_TOKEN-authored PRs don't trigger workflows → the required check never reports). homelab-ops — the governance this project mirrors (adr-0001) — does NOT hard-require any CI check; protect-main there is only deletion/non_fast_forward/ pull_request, and checks are signals merged manually/auto. Aligns commonplace to that: CI checks are signals; cc waits for green before self-merging; protect-main keeps PR-required + bypass_actors: []. A real hard gate is deferred to Phase D (GitHub App lets bot PRs trigger checks, no deadlock). - ROADMAP CI table: harness-ci / adr-pr-check -> "signal", with the rationale. - harness-ci.yml header: drop the obsolete "so it can be a required check" note. NOTE: the matching ruleset change (remove the required_status_checks rule from protect-main) is an operator action — the safety classifier blocks the agent from loosening a protected-branch control. Session-Id: 019e8d56-605a-7b45-8ef0-21ee576aa7a9 Agent: cc-rc-bot Co-authored-by: cyber-ayi <259769279+cyber-ayi@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Aligns commonplace's CI governance with homelab-ops (the upstream it mirrors,
adr-0001): CI checks are signals, not hard ruleset gates.Making
harness-cia required status check deadlocked theadr-assignnumbering PR —GITHUB_TOKEN-authored PRs don't trigger workflows, so the required check never reports. homelab-ops'sprotect-mainonly enforcesdeletion/non_fast_forward/pull_requestand merges bot PRs without a hard check gate.harness-ci.ymlheader → drop the obsolete "so it can be a required check" rationale.Operator action still needed
Remove the
required_status_checksrule from theprotect-mainruleset (the agent is blocked by the safety classifier from loosening a protected-branch control). After that,protect-main=deletion/non_fast_forward/pull_request, matching homelab-ops, and the numbering-PR deadlock is gone.Test plan
harness-cigreen on this PR (still required until the ruleset rule is removed)