-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add test cases for improving test coverage of release notes tools generator #11368
Comments
/triage accepted |
/help |
@sbueringer: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed 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-sigs/prow repository. |
Hey @sbueringer , I am interested in working on the issue. I am fairly new to contributing to this repository. Based on my understanding of the issue, the tool responsible for generating release notes is adding Release notes PR in the notes, which is not required. The test case should be making sure that this doesn't happen in the future - PRs with ":rocket:" 🚀 shouldn't be a part of release notes. Let me know if I am missing somethings. Thanks 😄 |
I think that's the idea, but maybe @chandankumar4 / @fabriziopandini had more in mind |
Hey @chandankumar4 |
Hey @irapandey |
@irapandey |
What would you like to be added (User Story)?
Add Unit test case for improving test coverage for release notes tools
Detailed Description
Reference: #10931 (comment)
Anything else you would like to add?
No response
Label(s) to be applied
/area testing
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.
The text was updated successfully, but these errors were encountered: