From 04941384f3bda9155ac105f6cd952318af45abff Mon Sep 17 00:00:00 2001 From: Keysat Date: Mon, 15 Jun 2026 21:27:59 -0500 Subject: [PATCH] Default git workflow to main with an approval-on-push gate Drop "commit directly to main" wording that sessions read as "make a feature branch"; make main the default and gate on push. --- how-i-work.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/how-i-work.md b/how-i-work.md index 9edb7f9..0cdafc9 100644 --- a/how-i-work.md +++ b/how-i-work.md @@ -26,8 +26,9 @@ Universal preferences for any coding agent working with me, on any project. Load - **No AI co-authorship attribution.** Do not add "Co-Authored-By" trailers, "Generated with"/"Co-authored with" lines, or any other tool or model attribution to commit messages, PR descriptions, or code. Commits are authored by me. - Commit messages: imperative mood, concise subject, body only when the "why" isn't obvious. -- Push to the configured remote after committing. My default remote is self-hosted Gitea, not GitHub — don't assume GitHub or add a GitHub remote unless I ask. -- Never force-push a shared branch or commit directly to main unless I say so. +- **Work on `main` (or the repo's default branch); don't create feature branches unless I ask.** These are solo, non-critical repos — my approval before pushing *is* the review gate, so branches and PRs only add ceremony. If a change is genuinely risky or experimental and you'd want to abandon it cleanly, suggest a branch — but `main` is the default and the branch is the exception. +- **Ask before pushing; don't auto-push after committing.** Once I approve, push straight to `main`. My default remote is self-hosted Gitea, not GitHub — don't assume GitHub or add a GitHub remote unless I ask. +- Never force-push a shared branch unless I say so. - Never commit secrets, large binaries, or generated artifacts. Documents reference env-var names only; real values live in gitignored .env files. ## Debugging