@@ -8,7 +8,7 @@ In my opinion, JSON should _never_ need to be written or read by humans, unless
## How to defer work
-Your suggestions are valuable and our findings while working are important. When we identify an issue, or you suggest improvements, fixes, etc., but I say we'll tackle them later, suggest creating a bug with `git-bug` so we don't lose that information. Any time we find a bug resulting from a commit, include the trailer `References: {SHORT_COMMIT_HASH}`. When we're working on a bug and realise we'll need to fix something later about our implementation of that bug resolution, include `References: bug-{SHORT_BUG_HASH}` trailer. For _all_ bugs, issues, todos, tickets, and comments you create, include yourself in the `Co-authored-by:` trailer at the bottom.
+Your suggestions are valuable and our findings while working are important. When we identify an issue, or you suggest improvements, fixes, etc., but I say we'll tackle them later, suggest creating a bug with `git-bug` so we don't lose that information. Any time we find a bug resulting from a commit, include the trailer `References: {SHORT_COMMIT_HASH}`. When we're working on a bug and realise we'll need to fix something later about our implementation of that bug resolution, include `References: bug-{SHORT_BUG_HASH}` trailer. For _all_ bugs, issues, todos, tickets, and comments you create, include yourself in the `Assisted-by: [Model Name] via [Tool Name]` trailer at the bottom.
# Preferred tooling
@@ -81,7 +81,7 @@ Create/amend commits exclusively using `formatted-commit`. Try to use it normall
-h --help
</formatted-commit_flags>
<formatted-commit_example>
-formatted-commit -t feat -s "web/git-bug" -m "do a fancy new thing" -T "Crush <crush@charm.land>" -b "$(cat <<'EOF'
+formatted-commit -t feat -s "web/git-bug" -m "do a fancy new thing" -T "Assisted-by: GLM 4.6 via Crush" -b "$(cat <<'EOF'
Multi-line
- Body
@@ -91,4 +91,6 @@ EOF
)"
</formatted-commit_example>
-When directed to sign commits, sign as `Crush <crush@charm.land>` as shown in the examples.
+# ALWAYS sign your work
+
+When signing commits, PRs, etc. make sure to include your metadata in an `Assisted-by: [Model Name] via [Tool Name]` footer, like "Assisted-by: Claude Sonnet 4.5 via OpenCode" or "Assisted-by: GPT-5 via Codex" or "Assisted-by: Qwen 3 Coder via Crush" and so on.