-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Implement PushToNamedFork in the git v2 client. #30971
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
Conversation
@cjwagner: GitHub didn't allow me to assign the following users: airbornepony. Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. 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/test-infra repository. |
|
||
for _, testCase := range testCases { | ||
t.Run(testCase.name, func(t *testing.T) { | ||
actual, actualErr := HttpResolver(testCase.remote, testCase.username, testCase.token, "org")() |
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.
The functionality that was tested here is well tested by the other test functions in this file. I updated the other test functions with unit cases to cover the new behavior.
d462274
to
6f48638
Compare
/retest |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andyzhangx, cjwagner The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I'm wondering if we can deploy the prow changes ASAP because cherrypicker is a frequently used utilility. @kubernetes/k8s-infra-group-admins |
I think this is a reasonable way to implement this, but I'm definitely open to alternative implementation suggestions. I tried to refactor the logic for the
httpResolverFactory
into something more readable.fixes #30937
/assign @airbornepony @timwangmusic
/cc @killianmuldoon