Erick Fejta
Erick Fejta
Note that an unfortunate side effect of this strategy is that it ignores any ENTRYPOINT defined by the image. The user will have to be careful to add the entrypoint...
Plugins could solve those issues, for example `/auto-assign` `/auto-assign-more`, `/rotate-assignees`, `/add-approver-for some/random/file` etc. The primary reason people need to see who is in a team is so that they can...
You cannot create a team and fix the team in the cycle https://github.com/kubernetes/test-infra/blob/0c1e01159b26a39d2a37de4d83cb18ab94747ed8/prow/cmd/peribolos/main.go#L831-L838 https://github.com/kubernetes/test-infra/blob/0c1e01159b26a39d2a37de4d83cb18ab94747ed8/prow/cmd/peribolos/main.go#L1052-L1072 You can't fix the details of a team that doesn't exist.
You can't fix something that doesn't exist
we should kill this tool and use the built-in one there is no reason for us to spend our time competing with bazel here. If we are unhappy the performance...
I know, and I'll take slow and functional over high maintenance costs every day of the week
Moving prow/cluster files into config/prow or somewhat like that sgtm
Can we: 1) Do most reporting on the commit, rather than the PR? 2) Optionally drop a note on the PR that postsubmits were scheduled to commit X and to...
> Considering the scenario in this review comment I don't think that scenario is correct. How/when do we imagine it would come about? In the scenario where we merge PR...
Is this looking for review again? Not sure.