Mercurial
comparison AGENT.md @ 222:a8d6435dc021 hg-web
[hg-web] Run local stack through Bazel
| author | MrJuneJune <me@mrjunejune.com> |
|---|---|
| date | Sun, 02 Aug 2026 09:07:36 -0700 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| 221:ce7f4400c2de | 222:a8d6435dc021 |
|---|---|
| 1 # Agent instructions | |
| 2 | |
| 3 ## Bazel is the project interface | |
| 4 | |
| 5 All project execution must happen through Bazel. Use existing `bazel build`, | |
| 6 `bazel test`, and `bazel run` targets instead of invoking compiled binaries, | |
| 7 language runtimes, package managers, generated scripts, or multiple services | |
| 8 manually. | |
| 9 | |
| 10 When a workflow needs several processes or commands, add a Bazel target that | |
| 11 owns their startup, runfiles, supervision, shutdown, and exit status. The user | |
| 12 should need one `bazel run` command. | |
| 13 | |
| 14 For hg-web development, run the complete local stack with: | |
| 15 | |
| 16 ```bash | |
| 17 bazel run //hg-web:dev | |
| 18 ``` | |
| 19 | |
| 20 Add or update the smallest relevant Bazel target whenever code cannot be built, | |
| 21 tested, run, bundled, or orchestrated through Bazel. |