-
Notifications
You must be signed in to change notification settings - Fork 827
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
Rename default branch for kubernetes/k8s.io #1597
Comments
@spiffxp: The label(s) 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. |
PR up for job config changes + prow config changes: kubernetes/test-infra#20675 (holding merge until next week, and completion of the below review) Still need to:
|
Merged kubernetes/test-infra#20675 |
Renamed the branch |
Will leave as-is and cleanup tomorrow Confirmed:
Known issues:
|
https://kubernetes.slack.com/archives/C1TU9EB9S/p1613578896224800 - @xmudrii noticed cs.k8s.io wasn't able to search this repo anymore, @dims enabled |
I'm going to assume the jobs that have no recent runs are fine given everything else worked |
Looking for references to
|
Still need to cleanup references to master in this repo Blocking
Nice to have
1 I would like to learn how to deploy k8s.io, but it may be a while before I can get there. |
/milestone v1.22 |
/help We could use some help closing out "clean up links to List generated via: curl -s -X POST \
-F "q=/k8s.io/(tree|blob)/master/" \
-F "repos=*" \
"https://cs.k8s.io/api/v1/search" \
| jq -r '.Results | keys | .[]' \
| sort \
| sed -e 's/^/- [ ] /g' EDIT: updated as of 2021-09-15
|
@spiffxp: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed 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. |
/assign |
Closed all my PRs except kubernetes-csi/csi-release-tools#164 Seems like we have a way to mass update all the repos |
/assign @anubha-v-ardhan @praveenghuge @RinkiyaKeDad Sounds like @pohly will help out with the remainder of the kubernetes-csi repos |
All the PRs for |
I refreshed #1597 (comment) and poked the open PRs I could find. There are still some outstanding repos I couldn't find a linked repo for. Leaving this in v1.22 because it may be basically done if we can figure out how many repos are blocked by the "csi tools will be copied" reasoning |
As I mentioned in kubernetes-sigs/nfs-ganesha-server-and-external-provisioner#55 (comment), repo owner are not blocked and can update their copy of csi-release-tools. |
/milestone v1.23 |
Unassinging myself for the moment, but please let me know if there's something that needs help :) /unassign |
Two more repos have crept up since this issue was created. So I opened:
And poked for an update on: |
Hopefully the last bit needed: |
/close Thanks for the help @RinkiyaKeDad @anubha-v-ardhan @pohly @wongma7 @ikarldasan @praveenghuge |
@spiffxp: 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/test-infra repository. |
Part of umbrella issue kubernetes/org#2222
Issue to spec out and then run through renaming the default branch for this repository
/sig contributor-experience
/area github-management
trialing a repo for this subproject
/wg k8s-infra
owns this repo
/sig testing
to discover any prow issues
/milestone v1.21
/priority important-soon
/assign @spiffxp
I plan on speccing this out, whether/when to execute depends on how kubernetes/org goes
The text was updated successfully, but these errors were encountered: