From f2a09726b40efabf87aae4c1167c64113abee5bf Mon Sep 17 00:00:00 2001 From: Amolith Date: Mon, 22 Dec 2025 10:59:07 -0700 Subject: [PATCH] chore(agents): update git-bug documentation Remove bug creation instructions and add status change commands. Assisted-by: Claude Opus 4.5 via Crush --- dot_config/AGENTS.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/dot_config/AGENTS.md b/dot_config/AGENTS.md index f62191b631ab2fbae71692b1e607b7ed2f7adbe0..f77d8c9557bcabfee5852065cd3aa37e62d74e55 100644 --- a/dot_config/AGENTS.md +++ b/dot_config/AGENTS.md @@ -80,16 +80,13 @@ IMPORTANT: When I ask you to plan first, I want you to first slow down and make ### git-bug -I like using a bug tracker that embeds bugs and identities and conversations directly in the repo we're working in. These can be private bugs just for me, or public bugs I push to the remote repo to collaborate on with other contributors. It's called `git-bug` and you interact with it like so. +I sometimes use a bug tracker that embeds bugs and identities and conversations directly in the repo we're working in. These can be private bugs just for me, or public bugs I push to the remote repo to collaborate on with other contributors. It's called `git-bug` and you interact with it like so. -- Create new bugs: `git-bug bug new [flags]` - - -t bug subject - - -m bug body - - -F accept the subject _and_ from the given files, use `-` to read from stdin. The first line is the subject, then include a blank line, then the body, then a blank line, then any trailers. - Commenting on a bug: `git-bug bug comment new [BUG_HASH] [flags]` - -m comment body - -F accept the message from the given files, use `-` to read from stdin - Viewing a bug's timeline: `git-bug bug show [BUG_HASH]` +- Closing or reopening a bug: `git-bug bug status close [BUG_HASH]` or `git-bug bug status open [BUG_HASH]` - Pushing and pulling: always pull before pushing - `git bugs-pull` - `git bugs-push`