From 7accb2616f53bcfedd99463b63fff6cdc0a94f9c Mon Sep 17 00:00:00 2001 From: Keysat Date: Mon, 15 Jun 2026 21:42:39 -0500 Subject: [PATCH] Make a single approval cover both commit and push Replace the two-gate "ask before pushing" wording: one approval is the go-ahead to commit and push to main in one step. --- how-i-work.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/how-i-work.md b/how-i-work.md index 0cdafc9..23f1511 100644 --- a/how-i-work.md +++ b/how-i-work.md @@ -27,7 +27,7 @@ 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. - **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. +- **Ask before committing; one approval covers both commit and push.** When I approve a change, that's the go-ahead to commit *and* push it to `main` in one step — don't commit and then ask again before pushing. 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.