Skip to content

Adopt GCL-ENGINEERING-001: engineering clarity and minimal architecture - #10

Merged
fyremael merged 2 commits into
mainfrom
governance/adopt-gcl-engineering-001-20261114
Nov 14, 2026
Merged

fyremael merged 2 commits into
mainfrom
governance/adopt-gcl-engineering-001-20261114

Conversation

@fyremael

Copy link
Copy Markdown

Adopt standard pinned at protected gcl-standards 2a3cfed9419ba9b74eeaaee70b9db8c3f47f3c9b; preserve reserved/domain-specific policy. Documentation entrypoint, no infrastructure. Require protected checks and readback.

@fyremael
fyremael requested a review from a team as a code owner November 14, 2026 11:55

Copy link
Copy Markdown
Author

GCL-ENGINEERING-001 rollout — exact protected admission blocker (2026-11-14)

Pinned engineering standard changes only AGENTS.md. ShellCheck PR workflow passed, but protected merge rejected because 2 of 3 required status checks are still expected and no results were produced for them. Combined legacy commit statuses are empty. Diagnose exact configured check contexts via repository rules/API with authorized admin access, restore their legitimate execution or correct stale rules through protected governance; do not manufacture a successful check or weaken protection to force this documentation merge.

Durable cross-repository ledger: https://github.com/grandchallenge/gcl-standards/blob/main/status/GCL-ENGINEERING-001-rollout.json . This PR remains open until its own protected gate is satisfied; no global completion claim.

@fyremael fyremael closed this Nov 14, 2026
@fyremael fyremael reopened this Nov 14, 2026

Copy link
Copy Markdown
Author

Further exact-rule diagnosis (2026-11-14): protected branch ruleset Provider profile - main requires policy / policy, security / action-policy, and routing-enforcement. Existing .github/workflows/gcl-conformance.yml is configured for pull_request, calls the organization's pinned policy/security reusable workflows, and previously emitted successful PR results in September. At this PR's exact head, GitHub's authenticated Actions run readback lists only the fork's ordinary CI and GH-OS routing enforcement; no GCL conformance run exists, leaving the two policy/security required checks unproduced. A bounded close/reopen test was attempted on lean-action PR #10; it successfully reran ShellCheck and GH-OS routing, but still did not launch GCL conformance. This is not a test failure to paper over. The remaining diagnostic obligation is workflow enabled-state / trigger suppression and the exact policy/security runner, which requires Actions-workflow administrative read/write access not exposed by the current connected GitHub installation; CHAD's authenticated command connector also currently fails. Preserve the required checks; repair the missing existing workflow trigger rather than weakening branch protection or fabricating statuses.

Copy link
Copy Markdown
Author

Bounded synchronization test completed on 2026-11-14. Updated AGENTS.md with a provider-specific reminder that shared-standard adoption must preserve Action behavior and required CI; exact new head 8b970e9ee7dd891f39600b990180a5a5530d7286. This generated the expected pull_request synchronize event: ShellCheck run 43598448587 PASSED and GH-OS routing run 43598446702 PASSED. The existing .github/workflows/gcl-conformance.yml, which declares on: pull_request, again produced no workflow run. This rules out a missing PR synchronize event and isolates the problem to GCL conformance workflow registration/eligibility/dispatch, not the PR change. Required checks remain policy / policy and security / action-policy, as read from protected ruleset 19965519. Do not push more diagnostic no-op commits or forge status. Investigate workflow enabled/disabled status and repository-level Actions restrictions using authorized Actions-admin readback; retain branch protection.

@fyremael
fyremael enabled auto-merge (squash) November 14, 2026 13:24
@fyremael fyremael closed this Nov 14, 2026
auto-merge was automatically disabled November 14, 2026 22:40

Pull request was closed

@fyremael fyremael reopened this Nov 14, 2026
@fyremael
fyremael merged commit f58ea91 into main Nov 14, 2026
6 checks passed
@fyremael
fyremael deleted the governance/adopt-gcl-engineering-001-20261114 branch November 14, 2026 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant