mirror of
https://github.com/carbon-language/carbon-lang.git
synced 2026-09-24 09:10:13 +01:00
Dana Jansens
413ac55d4f
Add rules to not overwrite git/jj history without asking, since this destroys the reviewer's view of things. And some information on dealing with stacks of commits within a single bookmark/PR. Prek can make fixes for whatever caused a failure, and then pass when you run it again, even though the user didn't change anything, and that is now explained. Assisted-by: Opus 5
1.0 KiB
1.0 KiB
Gemini & AI Assistant Guide for Carbon
This document provides high-density technical context for AI assistants contributing to the Carbon Language project.
General instructions
- Communication: Be concise, professional, and technical. Use GitHub-style markdown.
- Verification: Always run relevant tests.
Bazel usage
[!IMPORTANT] Always use
bazeliskinstead ofbazelfor all commands in the Carbon project. Refer to the Bazel usage skill for detailed instructions.
Version control
[!IMPORTANT] Never rewrite the history of a change that has been submitted as a pull request. Reviewers track a PR by its commits, and rewriting them discards their in-progress review. Ask before rewriting history in any case. Refer to the Jujutsu (jj) usage skill for details.