-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Prow issue: Bad invalid commit message for npm dependencies #28257
Comments
/sig testing |
Also, there's no way to disable this from re-applying repeatedly very annoying. |
Another PR with the same issue kubernetes-client/javascript#932 |
The bot also blocks Previously: #21534, we asked GitHub if we could alter this comment |
/sig contributor-experience |
+1 to Ben's comment. I don't think this is something we want to change globally at least. I could potentially see a repo+user exception, but i'd defer to sig-testing and the prow folk on it. |
How about a per-user exception? All of the PRs in question are sent by @dependabot which is unlikely to include any other users in it's comments. |
This continues to be a problem for the Javascript client as Even just the ability to manually disable it on a per-pr basis would be useful. |
@cjwagner not colew |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Migrated issue: kubernetes-sigs/prow#193 |
I got this error message on:
kubernetes-client/javascript#924
But in npm libraries, the
@
character is used to indicate an organization, even the default kubernetes client uses it@kubernetes/client-node
The text was updated successfully, but these errors were encountered: