docs+ci: refresh README for v2.1.0 + drop paths-ignore#32
Merged
Conversation
- Header banner rewrites the v2.0.11 paragraph for v2.1.0 (hotkeys, tray toggle, notification prefs, idle-only purge, single-instance signal, Memory card refresh). - Build snippet bumped 2.0.11 → 2.1.0 to match the current installer filename. - Version table gets a v2.1.0 "Current" row; v2.0.8/9/10 marked "Superseded by v2.0.11" so the table reflects the pre-release status those tags carry on GitHub. - License footer cites MIT explicitly + links to LICENSE. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Branch protection on main requires the "Build (Release)" status
check before merge. Paths-ignored events never publish a check at
all, so every docs-only PR (README, LICENSE) was silently
unmergeable — the API refused even admin bypass with "Repository
rule violations found: Required status check Build (Release) is
expected."
Three options were on the table:
(a) drop paths-ignore — every PR runs CI (~3 min cost)
(b) keep paths-ignore + add a no-op job that publishes the same
check name for docs-only changes (more workflow, same outcome)
(c) drop the required check (defeats branch protection)
(a) is simplest and keeps the rule "every PR runs CI" uniformly
true. The cost of a README CI run is negligible compared to the
recurring friction of skipped checks blocking merges.
Co-Authored-By: Claude Opus 4.7 <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
Two changes bundled because the workflow fix is what makes the README change mergeable in the first place.
1. README refreshed for v2.1.0
2.0.11→2.1.0.2. Workflow drops paths-ignore
Branch protection on main requires
Build (Release)before merge. Paths-ignored events never publish that check, so docs-only PRs were silently unmergeable — even admin merge bypass failed with "Repository rule violations found".Trade-off: every README change now triggers a ~3 min Windows CI run. Acceptable cost for the rule "every PR runs CI" being uniformly true. The previous PR #31 went through this exact deadlock; that PR is closed and this one supersedes it.
🤖 Generated with Claude Code