// Review that update/mutation logic has integration test coverage in test/integration/.
| name | integration-tests-for-updates |
| description | Review that update/mutation logic has integration test coverage in test/integration/. |
| license | Apache-2.0 |
| metadata | {"copyright":"The Kubernetes Authors"} |
Flag: New logic that handles an update case (as opposed to create or delete), with no corresponding integration test.
Ask: "Do we have an integration test covering this update scenario?" Unit tests alone are not sufficient — update paths are a common source of subtle bugs and should be covered in test/integration/.
Write or review Kueue PR release notes. Use when a user asks to draft, refine, validate, or combine release notes for a Kueue pull request, especially when deciding whether the note should be framed as a bugfix, feature, observability improvement, or breaking change.
Review that algorithm comments match the implementation. Use when a comment describes a formula or algorithm and you want to verify it matches what the code actually does.
Review that new CRD fields have complete godoc comments with enum value descriptions.
Review that paired operations and fields that always appear together are encapsulated in a helper or nested struct.
Review that local variables with unnecessarily wide scope are extracted into helper functions.
Review that new feature-gated behavior has explicit gate checks on all reachable code paths.
