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
Ensure `kind` is correct and fill the `summary` field with a brief description. You can ignore `component`, but you must set `pr`, `issue` and `repository` manually, the logic to fill them automatically is still work in progress.
61
+
Ensure `kind` is correct and fill the `summary` field with a brief description.
Copy file name to clipboardExpand all lines: internal/changelog/fragment/creator_internal_test.go
+8-5Lines changed: 8 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -94,16 +94,19 @@ summary: foobar
94
94
# Affected component; a word indicating the component this changeset affects.
95
95
component:
96
96
97
-
# PR number; optional; the PR number that added the changeset.
97
+
# PR URL; optional; the PR number that added the changeset.
98
98
# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added.
99
99
# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number.
100
100
# Please provide it if you are adding a fragment for a different PR.
101
-
#pr: 1234
101
+
#pr: https://github.com/owner/repo/1234
102
102
103
-
# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of).
103
+
# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of).
104
104
# If not present is automatically filled by the tooling with the issue linked to the PR number.
105
-
#issue: 1234
105
+
#issue: https://github.com/owner/repo/1234
106
106
`
107
107
got:=string(content)
108
-
assert.Equal(t, expected, got)
108
+
assert.Equal(t, expected, got, `This test exists to force review on changes to the Changelog Fragment template, as changing the template may introduce breaking changes.
109
+
This test is here to double check and confirm the choice of changing it. If the change introduce a breaking change, make sure to create a proper upgrade path for users.
110
+
If you changed the template and this test break, you know why.
0 commit comments