char-fork/llama.cpp

git clone https://git.t4t.associates/char-fork/llama.cpp

Georgi Gerganovtests : add fusion baseline README and broaden fusion CI triggers (#28893)bbdd9f246

char/aliceai-t5-moe
brancheschar/aliceai-t5-moeall refs →
1.8 KiB32 linesraw

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
  • When [MODEL] is needed, first try to get it from the PI_MODEL_NAME env var before asking the user

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]"
  • If PI_MODEL_NAME env var is not set, 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
  • Never reply to review comments or post comments on issues/PRs without explicit permission from the user

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
1You are a coding agent. Here are some very important rules that you must follow:
2
3General:
4- Be very precise and concise when writing code, comments, explanations, etc.
5- If an inline comment exceeds 2 lines, replace it with: `// note: TODO LATER`
6- PR and commit titles format: `<module> : <title>`. Lookup recents for examples
7- Don't try to build or run the code unless you are explicitly asked to do so
8- Use the `gh` CLI tool when querying PRs, issues, or other GitHub resources
9- When [MODEL] is needed, first try to get it from the `PI_MODEL_NAME` env var before asking the user
10
11Coding:
12- When in doubt, always refer to the CONTRIBUTING.md file of the project
13- In `test-backend-ops.cpp`, do not mention specific backends (e.g. Metal, CUDA) in comments
14- When referencing issues or PRs in comments, use the format:
15  - C/C++ code: `// ref: <url>`
16  - Other (CMake, etc.): `# ref: <url>`
17
18Pull requests (PRs):
19- New branch names are prefixed with "gg/"
20- Before opening a pull request, ask the user to confirm the description
21- Don't explicitly wrap lines in the PR description (each paragraph and bullet is a single line)
22- When creating a pull request, look for the repository's PR template and follow it
23- For the AI usage disclosure section, write "YES. pi:llama.cpp/[MODEL]"
24- If `PI_MODEL_NAME` env var is not set, ask the user to tell you what model was used and write it in place of [MODEL]
25- Always create the pull requests in draft mode
26- Never reply to review comments or post comments on issues/PRs without explicit permission from the user
27
28Commits:
29- On every commit that you make, include a "Assisted-by: pi:llama.cpp/[MODEL]" tag
30- Do not explicitly set the git author in commits - rely on the default git config
31- Always use `--no-gpg-sign` when committing
32- Never `git push` without explicit confirmation from the user