Files
Georgi Gerganov 3a653fea93 ci : add older, min and dry-run options to ccache-clear (#27504)
* ci : add older, min and dry-run options to ccache-clear

Assisted-by: pi:llama.cpp/Qwen3.8-27B

* pi : add note about not wrapping lines in PR descriptions

[no ci]

Assisted-by: pi:llama.cpp/Qwen3.8-27B
2026-08-22 11:31:30 +03:00

1.6 KiB

You are a coding agent. Here are some very important rules that you must follow:

General:

  • Be very precise and concise when writing code, comments, explanations, etc.
  • If an inline comment exceeds 2 lines, replace it with: // note: TODO LATER
  • PR and commit titles format: <module> : <title>. Lookup recents for examples
  • Don't try to build or run the code unless you are explicitly asked to do so
  • Use the gh CLI tool when querying PRs, issues, or other GitHub resources

Coding:

  • When in doubt, always refer to the CONTRIBUTING.md file of the project
  • In test-backend-ops.cpp, do not mention specific backends (e.g. Metal, CUDA) in comments
  • When referencing issues or PRs in comments, use the format:
    • C/C++ code: // ref: <url>
    • Other (CMake, etc.): # ref: <url>

Pull requests (PRs):

  • New branch names are prefixed with "gg/"
  • Before opening a pull request, ask the user to confirm the description
  • Don't explicitly wrap lines in the PR description (each paragraph and bullet is a single line)
  • When creating a pull request, look for the repository's PR template and follow it
  • For the AI usage disclosure section, write "YES. pi:llama.cpp/[MODEL]"
  • Ask the user to tell you what model was used and write it in place of [MODEL]
  • Always create the pull requests in draft mode

Commits:

  • On every commit that you make, include a "Assisted-by: pi:llama.cpp/[MODEL]" tag
  • Do not explicitly set the git author in commits - rely on the default git config
  • Always use --no-gpg-sign when committing
  • Never git push without explicit confirmation from the user