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

Simplify Release Notes section of the PR checklist #5094

Merged
merged 1 commit into from
Jul 7, 2022

Conversation

dibyom
Copy link
Member

@dibyom dibyom commented Jul 6, 2022

Changes

This commit simplifies the release notes section by replacing the existing
comment with a default NONE release note. In addition it updates the
submitter checklist instruction to expect the submitter to update the release
note if needed. In addition, it adds two new items to the checklist - 1. to add
a kind label using the /kind command and 2. add an action required: to the
release note if needed.

Fixes #5093

Signed-off-by: Dibyo Mukherjee [email protected]

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Docs included if any changes are user facing
  • Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Release notes block below has been filled in
    (if there are no user facing changes, use release note "NONE")

Release Notes

NONE

This commit simplifies the release notes section by replacing the existing
comment with a default `NONE` release note. In addition it updates the
submitter checklist instruction to expect the submitter to update the release
note if needed. In addition, it adds two new items to the checklist - 1. to add
a kind label using the /kind command and 2. add an `action required:` to the
release note if needed.

Fixes tektoncd#5093

Signed-off-by: Dibyo Mukherjee <[email protected]>
@tekton-robot tekton-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 6, 2022
@tekton-robot tekton-robot requested review from imjasonh and lbernick July 6, 2022 21:54
@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jul 6, 2022
@dibyom
Copy link
Member Author

dibyom commented Jul 6, 2022

As a case in point, I copy pasted the example release note from the instructions but because I forgot to remove the extra space between the backticks and release-note, I got the do-not-merge/release-note-label-neeeded label 😒

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 7, 2022
@vdemeester
Copy link
Member

/kind misc

@tekton-robot tekton-robot added the kind/misc Categorizes issue or PR as a miscellaneuous one. label Jul 7, 2022
@vdemeester
Copy link
Member

/retest
cloud event unit test flaky (again..)

```

For pull requests that don't need to be mentioned at release time, use the `/release-note-none` Prow command to add the `release-note-none` label to the PR. You can also write the string "NONE" as a release note in your PR description:

``` release-note
Copy link
Member

Choose a reason for hiding this comment

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

I would remove the space between the ticks and release-note - it's very hard to spot so many PRs fail the release notes check because of that

Copy link
Member

Choose a reason for hiding this comment

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

So we added it to make sure it would "fail" the check and make contributors look at it (described in the comment).
If we don't, by default all pr will have release-note-none and no message telling the user about release-note 🙃

Copy link
Member

Choose a reason for hiding this comment

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

I know, but TBH I find it a bit confusing... we have the checkbox about setting the release notes now, hopefully that's enough?

Copy link
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

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

Thanks for this!
/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2022
@tekton-robot tekton-robot merged commit 7cd2e91 into tektoncd:main Jul 7, 2022
@dibyom dibyom deleted the relnote branch July 7, 2022 14:34
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. kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. 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.

Simplify Release Notes section of our PR checklist
4 participants