Git Commit & PR

Trigger Conditions

Execution Steps

1. Create a new branch:

   git checkout -b <branch-name>

   , where the branch name is specified by the user or automatically generated based on the changes.
2. Review changes: First use

   git status

   and

   git diff

   to check all changes yourself, ensuring no temporary files, debug code, or unrelated files are included.
3. Stage files: Use

   git add

   to add relevant changed files. Do not use

   git add -A

   or

   git add .

   ; instead, add relevant files one by one.
4. Commit changes:
   bash

   git commit --signoff --author="Cheney Zhang <chen.zhang@zilliz.com>" -m "<commit message>"

   • Write the commit message in English, concisely describing the changes.
   • Never mention AI, Claude, LLM, or any auto-generation-related terms in the commit message.
5. Push the branch:

   git push origin <branch-name>

   .
6. Create PR:
   bash

   gh pr create --repo <official-owner/repo> --title "<PR title>" --body "<PR description>"

   • Write the PR title and description in English.
   • Never mention AI, Claude, LLM, or any auto-generation-related terms in the PR title or description.
   • Do not add AI-related tags like

     Co-Authored-By

     .
7. If the user has merge permissions and requests merging:
   • Review the PR and merge it.
   • Switch back to the main branch (main or master).
   • Sync with upstream:

     git fetch official && git reset --hard official/<main-branch>

     .
   • Delete the local temporary branch:

     git branch -d <branch-name>

     .
   • Delete the remote temporary branch:

     git push origin --delete <branch-name>

     .

Notes

• First confirm that the

  official

  remote exists; if not, prompt the user to configure it first.
• Check if there are any unstaged changes that need to be handled before committing.
• All externally visible text (commit message, PR title/description) must not contain any AI-related terms.