Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preserve markdown order when generating release notes #875

Merged
merged 1 commit into from
Sep 28, 2019
Merged

Preserve markdown order when generating release notes #875

merged 1 commit into from
Sep 28, 2019

Conversation

saschagrunert
Copy link
Member

The markdown notes are now generated in historical order with the newest entries on the top of the document.

PS: I took my freedom to rename ReleaseNoteList to ReleaseNotes, since it is no actual type of list/slice.

The markdown notes are now generated in historical order with the newest
entries on the top of the document.

Signed-off-by: Sascha Grunert <sgrunert@suse.com>
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Sep 9, 2019
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. labels Sep 9, 2019
@idealhack idealhack removed their request for review September 11, 2019 15:42
@@ -31,7 +31,9 @@ func CreateDocument(notes ReleaseNoteList) (*Document, error) {
Uncategorized: []string{},
}

for _, note := range notes {
for _, pr := range history {
note := notes[pr]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't think of any case where something in the history wouldn't also be in notes (that would require a previously-merged PR disappearing) but it might be good/safe to trap that edge case in the future.

Copy link
Member

@jeefy jeefy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small discussion point but really
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 28, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jeefy, saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 28, 2019
@k8s-ci-robot k8s-ci-robot merged commit dd5bda8 into kubernetes:master Sep 28, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.17 milestone Sep 28, 2019
@saschagrunert saschagrunert deleted the markdown-order branch September 28, 2019 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/release Categorizes an issue or PR as relevant to SIG Release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants