Closed khrm closed 1 year ago
/release-note-none
@khrm: you can only set the release note label to release-note-none if the release-note block in the PR body text is empty or "none".
/release-note-none
@khrm: you can only set the release note label to release-note-none if the release-note block in the PR body text is empty or "none".
Added a release note - this is an important change that users and developers should know about!
We should not block on adding "user friendly" docs. I have filed #475 for this purpose - the docs "meets min" is that the auto-generated docs are synced with code.
Any progress?
@adambkaplan We have already integrated with the hub cli. So no new unchartered territory here.
@enarha @sayan-biswas @alan-ghelardi We also want to merge this before the release.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: adambkaplan, sayan-biswas
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Changes
Added annotations to support command integration with
tkn
.Submitter Checklist
These are the criteria that every PR should meet, please check them off as you review them:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes