You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. By default, `LATENCY_PREDICTOR_TAG` in the `Makefile` resolves from the router release tag (via `BUILD_REF`). If the latency predictor tag does **not** align with the router version, update the default value of `LATENCY_PREDICTOR_TAG` in the `Makefile` to match your exported `${LATENCY_PREDICTOR_TAG}`.
Copy file name to clipboardExpand all lines: AGENTS.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,12 @@ llm-d Router. Go service that routes inference requests to model-serving pods vi
30
30
- The PR addresses that issue and nothing else: no renames, reformatting, refactors, new abstractions, or pattern changes beyond what the issue requires.
31
31
- Unrelated improvements belong in their own issue and PR, not folded into this PR. If you spot dead code or unrelated bugs in passing, mention them; don't fix them.
32
32
- Self-check on the way out: if the change grew larger than expected or the fix feels hacky, rewrite the clean version before opening the PR.
33
+
- Verify the code passs `make presubmit` locally before submitting a PR.
34
+
- Always use the project's `.github/PULL_REQUEST_TEMPLATE.md`.
35
+
- Document user (not developer) facing changes in the ```release-note``` block. The `release-notes.d/unreleased/*`
36
+
file is automatically generated from the block's content - do not create the file directly.
37
+
- If you include a test plan section, mark passing tests with [x] so it is clear which ran and passed.
38
+
List only new tests - indicate functionality verified, not the test names.
0 commit comments