From 29a2cc51732003d775fddf927653b0fc94fe50ca Mon Sep 17 00:00:00 2001 From: Mike Wills Date: Wed, 15 Jul 2026 13:08:39 -0500 Subject: [PATCH] Require a branch + PR for all changes, never push directly to master 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 Claude-Session: https://claude.ai/code/session_01CfWmHii9XYmPNBhz5dGDxZ --- CLAUDE.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 1a2a02a..2e4c5b8 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -152,6 +152,14 @@ All filters are query parameters to `api.weather.gov`. Do **not** pull all alert - `LogError` — failures (API errors, exceptions) - Platform name as first token: `"Facebook: Post failed. Status={Status}"` +### 8. Always work on a branch and open a pull request — never push directly to `master` + +Even for a single small fix. Create a feature branch, commit there, push it, and open a PR with +`gh pr create` — then stop and let the human merge it (or explicitly ask before merging). Do not +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. + --- ## Key External APIs