🌱 Improve release notes formatting #8826
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
area/release
k8s-ci-robot
added
the
size/L
|
/hold |
k8s-ci-robot
added
the
do-not-merge/hold
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
LGTM label has been added. Git tree hash: 948bbe3698155702867a9afc681fb2a12e1dab58
|
k8s-ci-robot
removed
the
lgtm
g-gaston
force-pushed
the
release-notes-formatting-tweaks
branch
from
513526a
to
eae3326
Compare
g-gaston
force-pushed
the
release-notes-formatting-tweaks
branch
from
55a1057
to
01aabab
Compare
|
lgtm pending rebase on top of #8817 |
* Capitalize/shorten some area labels into more legible prefixes * Remove backport PR prefixes "[release-x.x]" * Omit "num of change of type x" lines when there are no changes of that kind (eg. no breaking changes) * Handle unsync emoji and documentation area
g-gaston
force-pushed
the
release-notes-formatting-tweaks
branch
from
01aabab
to
410cf44
Compare
k8s-ci-robot
added
size/M
|
@fabriziopandini rebased 🙌🏻 |
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
LGTM label has been added. Git tree hash: 02dfafb5881b193171f5661642df960f572ef002
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: killianmuldoon 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 |
k8s-ci-robot
added
the
approved
|
/unhold |
k8s-ci-robot
removed
the
do-not-merge/hold
killianmuldoon
pushed a commit
to killianmuldoon/cluster-api
that referenced
this pull request
Jun 15, 2023
…ormatting-tweaks 🌱 Improve release notes formatting
35 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
A few life of quality improvements that automate manual steps performed to cleanup the release notes:
that kind (eg. no breaking changes)
documentationto classify PRs that have the wrong emoji prefix in the title. We have seen in the past PR that use the 🐛 or 🌱 instead of 📖 , but they have thearea/documentationlabel. In these cases, the label tends to be more reliable than the PR title, so this PR makes the label take precedence.I put the last item in a separate commit, since we weren't completely sure if we wanted to automate this yet and if so, what should be the logic. Opening the conversation here.
Builds on top of #8817, so this needs to wait until that's merged. Review only the last two commits pls.
/area release