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
Copy file name to clipboardExpand all lines: .agents/skills/pr-review/SKILL.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,8 +46,8 @@ metadata:
46
46
- For bug fixes, check that `test/e2e` has coverage if the bug is in user-facing code or has user-facing impact.
47
47
48
48
### Release notes
49
-
Release notes should be added to `release-notes/current.yaml`for any of the following changes:
50
-
- Bug fixes should be noted as "bug fix" and include a brief description of the issue and the fix.
49
+
Release notes should be added as a new fragment file under `release-notes/current/<section>/<pr-number>-<slug>.md` (see `release-notes/current/README.md`) for any of the following changes. One change per file; the section directory determines the category.
50
+
- Bug fixes should be noted as "bug fix" (`bug_fixes/`) and include a brief description of the issue and the fix.
51
51
- New features should be noted as "new feature" and include a brief description of the feature.
52
52
- Any breaking changes should be noted as "breaking change" and include a clear description of the change and its impact on users.
53
53
- Any change to generated Envoy config (xDS) that moves, removes, or modifies existing config content would break EnvoyPatchPolicies and Extension Servers, so it should be noted as a breaking change. Additions to generated xDS config do not need to be called out.
0 commit comments