PR #156

9 votes · 9 up · 0 down

View on GitHub
9
Total Votes
+9
Upvotes
-0
Downvotes
+9-0

Comments(4)

bigintersmindComment#156README is the clear guide, RULES.md steps aside

Why automerge skipped this PR

This PR has 7 net votes, a rhyming title, passing CI, and no merge conflicts — it should have won today's daily merge. However, it was skipped because the combined commit status API returns pending.

Root cause: The branch protection rules for main require a status check named CI (the workflow name), but GitHub Actions only reports status for individual jobs (CI / build, CI / protect-constitution). The CI check is perpetually stuck at "Expected — Waiting for status to be reported" on every PR, which makes the combined status pending, which the automerge workflow treats as a hard skip.

Fix: In the repo's branch protection settings for main, remove the required status check CI and replace it with CI / build. This will unblock automerge for this PR and all others affected (#187, #193, #160, #183, #209).

lens0021Comment#156README is the clear guide, RULES.md steps aside

shortly closing as I prefer 207

DavieyComment#156Clarify that RULES.md is deprecated and README contains current rules

👎 Documentation clarification, boring

openchaos-bot[bot]Comment#156Clarify that RULES.md is deprecated and README contains current rules

🤖 OpenChaos Bot

Summary: This PR updates the README to indicate that the RULES.md file is deprecated and that all current rules are in the README.

Files changed: 1 (README.md)

Vibe: Burying the past to pave the way for a more README-centric future.


openchaos-bot

All Activity(15)

bigintersmindComment#156README is the clear guide, RULES.md steps aside

Why automerge skipped this PR

This PR has 7 net votes, a rhyming title, passing CI, and no merge conflicts — it should have won today's daily merge. However, it was skipped because the combined commit status API returns pending.

Root cause: The branch protection rules for main require a status check named CI (the workflow name), but GitHub Actions only reports status for individual jobs (CI / build, CI / protect-constitution). The CI check is perpetually stuck at "Expected — Waiting for status to be reported" on every PR, which makes the combined status pending, which the automerge workflow treats as a hard skip.

Fix: In the repo's branch protection settings for main, remove the required status check CI and replace it with CI / build. This will unblock automerge for this PR and all others affected (#187, #193, #160, #183, #209).

lens0021Comment#156README is the clear guide, RULES.md steps aside

shortly closing as I prefer 207

DavieyComment#156Clarify that RULES.md is deprecated and README contains current rules

👎 Documentation clarification, boring

openchaos-bot[bot]Comment#156Clarify that RULES.md is deprecated and README contains current rules

🤖 OpenChaos Bot

Summary: This PR updates the README to indicate that the RULES.md file is deprecated and that all current rules are in the README.

Files changed: 1 (README.md)

Vibe: Burying the past to pave the way for a more README-centric future.


openchaos-bot