-
Notifications
You must be signed in to change notification settings - Fork 436
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
feat(ci): add missing feat label checker #6451
feat(ci): add missing feat label checker #6451
Conversation
Co-authored-by: Brent Shaffer <betterbrent@google.com>
Co-authored-by: Brent Shaffer <betterbrent@google.com>
Co-authored-by: Brent Shaffer <betterbrent@google.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have any PRs where we've tested this?
This can be done by opening a new PR from a branch forked from this one, labeled feat
instead of chore
but with a new class or method added. This check should fail.
Co-authored-by: Brent Shaffer <betterbrent@google.com>
Actually, no. Because we need an owlbot PR to test this, so I could not raise one. |
You can just comment out this line in the test PR and then you can test it manually. |
Hi @bshaffer, thanks for the tip. I performed the tests and wrote the results here: #6481 (comment) Following up on the tests, I made following changes to the PR:
One thing to note is that, when a new function is added the failure message says function is removed instead of added: |
Yes, I think we may want to do some bash foo here to catch the exception message and throw a different one. And we can get rid of the PR annotations (by removing |
@bshaffer I added just a single print statement and pass/fail for that, PTAL |
Addresses #6397