Skip to content

Require a branch + PR for all changes#28

Merged
MikeWills merged 1 commit into
masterfrom
chore/pr-only-workflow
Jul 15, 2026
Merged

Require a branch + PR for all changes#28
MikeWills merged 1 commit into
masterfrom
chore/pr-only-workflow

Conversation

@MikeWills

Copy link
Copy Markdown
Owner

Summary

  • Codifies a workflow rule in CLAUDE.md: always work on a branch and open a PR, never push directly to master, even for small fixes.

Why

This session's Details-link fix went straight to master, bypassing the required "test" status check. The user asked to always use PRs going forward so CI actually gates changes.

Test plan

  • Docs-only change; no build/test impact.

https://claude.ai/code/session_01CfWmHii9XYmPNBhz5dGDxZ

Codifies a workflow preference the user gave after this session's Details-link
fix went straight to master, bypassing master's required "test" status check.
A PR is what actually runs dotnet test before anything lands.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CfWmHii9XYmPNBhz5dGDxZ
Comment thread CLAUDE.md
Comment on lines +159 to +162
push straight to `master`, and do not merge a PR yourself unless explicitly told to. `master`'s
branch protection allows this repo's owner to bypass its required "test" status check, but
bypassing it skips CI entirely — a PR is what actually runs `dotnet test` before anything lands.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Factual inaccuracy: "bypassing it skips CI entirely" isn't accurate for this repo. .github/workflows/deploy.yml triggers on every push to master and has its own dotnet test step (a deploy-time safety net), and .github/workflows/ci.yml's test job also triggers on push: branches: [master] in addition to pull_request. So a direct push to master still runs dotnet test in both workflows — it just isn't gated before the push lands. The rationale here would be more accurate as something like "bypassing it skips the pre-merge gate — tests still run post-push in deploy.yml/ci.yml, but a broken change can already be on master by the time they fail."

NwsAlertBot/CLAUDE.md

Lines 159 to 162 in 29a2cc5

push straight to `master`, and do not merge a PR yourself unless explicitly told to. `master`'s
branch protection allows this repo's owner to bypass its required "test" status check, but
bypassing it skips CI entirely — a PR is what actually runs `dotnet test` before anything lands.

@MikeWills
MikeWills merged commit 49438e8 into master Jul 15, 2026
4 checks passed
@MikeWills
MikeWills deleted the chore/pr-only-workflow branch July 15, 2026 18:36
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