diff options
| author | Dax Raad <[email protected]> | 2025-08-11 14:30:18 -0400 |
|---|---|---|
| committer | opencode <[email protected]> | 2025-08-11 18:36:06 +0000 |
| commit | 22023fa9e73513e0ff677646cc3fe18785c5635c (patch) | |
| tree | 92fc33da77c4e250717e3ac02d33316e320de2d8 | |
| parent | 85e0b53c33fff08d06561dd309382f7ff6f5bd27 (diff) | |
| download | opencode-22023fa9e73513e0ff677646cc3fe18785c5635c.tar.gz opencode-22023fa9e73513e0ff677646cc3fe18785c5635c.zip | |
remove git bash tool coauthor message
| -rw-r--r-- | packages/opencode/src/tool/bash.txt | 23 |
1 files changed, 0 insertions, 23 deletions
diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index caf2515ed..ce78347e0 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -59,10 +59,6 @@ When the user asks you to create a new git commit, follow these steps carefully: 3. You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS run the following commands in parallel: - Add relevant untracked files to the staging area. - - Create the commit with a message ending with: - 🤖 Generated with [opencode](https://opencode.ai) - - Co-Authored-By: opencode <[email protected]> - Run git status to make sure the commit succeeded. 4. If the commit fails due to pre-commit hook changes, retry the commit ONCE to include these automated changes. If it fails again, it usually means a pre-commit hook is preventing the commit. If the commit succeeds but you notice that files were modified by the pre-commit hook, you MUST amend your commit to include them. @@ -76,17 +72,6 @@ Important notes: - If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit - Ensure your commit message is meaningful and concise. It should explain the purpose of the changes, not just describe them. - Return an empty response - the user will see the git output directly -- In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC, a la this example: -<example> -git commit -m "$(cat <<'EOF' - Commit message here. - - 🤖 Generated with [opencode](https://opencode.ai) - - Co-Authored-By: opencode <[email protected]> - EOF - )" -</example> # Creating pull requests Use the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed. @@ -125,14 +110,6 @@ gh pr create --title "the pr title" --body "$(cat <<'EOF' ## Summary <1-3 bullet points> -## Test plan -[Checklist of TODOs for testing the pull request...] - -🤖 Generated with [opencode](https://opencode.ai) -EOF -)" -</example> - Important: - NEVER update the git config - Return the PR URL when you're done, so the user can see it |