DO NOT MERGE: A/B probe - reusable-quality pin @v1 -> @main#105
DO NOT MERGE: A/B probe - reusable-quality pin @v1 -> @main#105Prekzursil wants to merge 1 commit into
Conversation
Evidence artifact for the "is it safe to move the v1 tag in quality-zero-platform" decision. Repins reusable-quality.yml from @v1 to @main so CI here executes the 20-commits-ahead template that moving the tag would publish to every consumer. Carries the same single comment line as the control branch, so control vs probe differ by exactly one variable: the pin. Not for merge. Close when the tag decision is recorded.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2f0485345f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| jobs: | ||
| quality: | ||
| uses: Prekzursil/quality-zero-platform/.github/workflows/reusable-quality.yml@v1 | ||
| uses: Prekzursil/quality-zero-platform/.github/workflows/reusable-quality.yml@main |
There was a problem hiding this comment.
If this probe is merged, every subsequent push and pull request will execute whichever reusable workflow happens to be on the external repository's main branch at dispatch time, so unreviewed upstream changes can alter, break, or weaken this repository's required quality checks without any local commit. Keep this probe off the merge target or replace @main with a vetted immutable commit SHA before merging so verification remains deterministic.
AGENTS.md reference: AGENTS.md:L5-L6
Useful? React with 👍 / 👎.
|
Closing: deliberate A/B evidence artifact; the decision it informed is executed. Purpose was to measure whether moving the quality-zero-platform v1 tag was safe, using paired control (@v1) and probe (@main) arms on the same tree with one variable. Across 4 consumer pairs: 24 of 24 step names and conclusions byte-identical. The only differences were the gate-deps fix behaving as designed - a real finding at exit 1 still blocks, so it is fail-closed, not fail-open. Outcome: v1 moved from b9503300 to b4fbe384, then independently verified on a live consumer where a run that had failed twice under the old tag passed under the new one. Never intended to merge; evidence and CI links stay readable here. Reopen if the tag move needs re-litigating. |
1 participant
DO NOT MERGE: A/B probe arm (pin @v1 -> @main)
Evidence artifact for the "is it safe to move the v1 tag in
quality-zero-platform" decision. Repins reusable-quality.yml from @v1 to @main
so CI here executes the 20-commits-ahead template that moving the tag would
publish to every consumer.
Carries the same single comment line as the control branch, so control vs probe
differ by exactly one variable: the pin.
Not for merge. Close when the tag decision is recorded.