-
Notifications
You must be signed in to change notification settings - Fork 504
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
fix link to example go-template for release tool #3216
fix link to example go-template for release tool #3216
Conversation
Signed-off-by: Michael Shen <mishen@umich.edu>
Welcome @mjlshen! |
Hi @mjlshen. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mjlshen, 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 |
The test got rate-limited
/test pull-release-integration-test |
@mjlshen: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest |
/ok-to-test |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
I was looking into using the release-notes tool in this repo and noticed that the documentation pointed to an example template that has since been moved.
Which issue(s) this PR fixes:
None
Does this PR introduce a user-facing change?