docs: keep current-tip checks and reviews required

This commit is contained in:
mateo-berri 2026-10-20 12:35:32 -07:00
parent c029234907
commit 36fdfe184c

View file

@ -86,7 +86,7 @@ If you're seeing a delay in your PR being merged, ping the LiteLLM Team on [Slac
## Screenshots / Proof of Fix
<!-- Show end-to-end commands and observed output, screenshots, or recordings. Use real providers and paid LLM calls when applicable. Mocks and pytest output alone are insufficient
Show the latest applicable run, Before at the merge base and After at a commit containing the latest behavior change. A later tip may reuse proof only after reviewing the entire intervening diff and verifying tested behavior is unchanged, including behavior-neutral refactors. Keep the tested SHA and record the current tip, intervening changes, why proof remains valid, and focused checks. Docs, tests, or formatting alone need no live rerun, unless documentation is the product. Rerun affected QA for behavior, configuration, dependency, migration, or security changes, or uncertainty. Reuse Before only while its baseline remains valid. Never relabel old evidence as a new run
Show the latest applicable run, Before at the merge base and After at a commit containing the latest behavior change. A later tip may reuse proof only after reviewing the entire intervening diff and verifying tested behavior is unchanged, including behavior-neutral refactors. Keep the tested SHA and record the current tip, intervening changes, why proof remains valid, and focused checks. Docs, tests, or formatting alone need no live rerun, unless documentation is the product. Rerun affected QA for behavior, configuration, dependency, migration, or security changes, or uncertainty. Reuse Before only while its baseline remains valid. Never relabel old evidence as a new run. Required checks and reviews still apply to the current tip
Use Before and After headings below this section, each naming the tested SHA. Use the same case names and order on both sides, with numbered command and observed-output steps under each. Put shared config and payloads above Before. For one case, omit the case headings and number steps directly
### Before (<hash>)