-
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
"Details" link for "tide" check on GitHub PRs doesn't work for PRs authored by bot users #31694
Comments
/sig testing |
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 |
/remove-lifecycle stale |
Seems like a valid bug, would you mind re-filing this against https://github.com/kubernetes-sigs/prow ? (unfortunately github's "transfer" functionality doesn't work across organizations) |
Will do, thanks! |
Moved this here: kubernetes-sigs/prow#177 /close |
@nojnhuh: Closing this issue. 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. |
thanks! |
What happened:
e.g. For this dependabot PR: kubernetes-sigs/cluster-api-provider-azure#4496
This link matches no PRs:
https://prow.k8s.io/pr?query=is%3Apr+repo%3Akubernetes-sigs%2Fcluster-api-provider-azure+author%3Adependabot+head%3Adependabot%2Fgithub_actions%2Factions%2Fcache-4.0.0
What you expected to happen:
The query should be updated to query for the user
app/dependabot
instead ofdependabot
:https://prow.k8s.io/pr?query=is%3Apr%20repo%3Akubernetes-sigs%2Fcluster-api-provider-azure%20author%3Aapp%2Fdependabot%20head%3Adependabot%2Fgithub_actions%2Factions%2Fcache-4.0.0
How to reproduce it (as minimally and precisely as possible):
Please provide links to example occurrences, if any:
Anything else we need to know?:
The text was updated successfully, but these errors were encountered: