Browse Source

📝 docs: clarify git push instruction in commit command

darrenhinde 7 months ago
parent
commit
2ca29f0e6f
1 changed files with 1 additions and 1 deletions
  1. 1 1
      .opencode/command/commit.md

+ 1 - 1
.opencode/command/commit.md

@@ -155,6 +155,6 @@ Example commit sequence:
 - **Error handling**: If validation fails, give user option to proceed or fix issues first  
 - **Error handling**: If validation fails, give user option to proceed or fix issues first  
 - **Auto-staging**: If no files are staged, automatically stage all changes with `git add .`
 - **Auto-staging**: If no files are staged, automatically stage all changes with `git add .`
 - **File priority**: If files are already staged, only commit those specific files
 - **File priority**: If files are already staged, only commit those specific files
-- **Always run and push the commit**: You don't need to ask for confirmation unless there is a big issue or error.
+- **Always run and push the commit**: You don't need to ask for confirmation unless there is a big issue or error `git push`.
 - **Message quality**: Ensure commit messages are clear, concise, and follow conventional format
 - **Message quality**: Ensure commit messages are clear, concise, and follow conventional format
 - **Success feedback**: After successful commit, show commit hash and brief summary
 - **Success feedback**: After successful commit, show commit hash and brief summary