Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Rename the default branch in our repositories #391

Open
2 tasks
codificat opened this issue Mar 9, 2022 · 10 comments
Open
2 tasks

Rename the default branch in our repositories #391

codificat opened this issue Mar 9, 2022 · 10 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@codificat
Copy link
Member

Problem statement

Most of our repositories still use master as the default branch's name.

High-level Goals

Use main as the default branch's name.

Proposal description

Change the default branch on existing repositories so that we use main instead of master.

Additional context

https://github.com/github/renaming

Acceptance Criteria

  • All repositories under thoth-station use main as their default branch
  • Any references to master have been corrected to reflect the change
@codificat codificat added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels Mar 9, 2022
@codificat
Copy link
Member Author

/priority important-longterm
/triage accepted

@sesheta sesheta added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels Mar 23, 2022
@Gregory-Pereira Gregory-Pereira mentioned this issue Mar 31, 2022
Merged
@goern
Copy link
Member

goern commented Apr 4, 2022

/sig user-experience

@sesheta sesheta added the sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. label Apr 4, 2022
@sesheta
Copy link
Member

sesheta commented Jul 3, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 3, 2022
@sesheta
Copy link
Member

sesheta commented Aug 2, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 2, 2022
@VannTen
Copy link
Member

VannTen commented Aug 18, 2022

What are the references to master we use, besides local git repos ?

Apparently everything on github besides github actions is retargeted/redirected
automatically.

I did not see a way to rename in branch in bulk on all org repos, but maybe
there is a GraphQl endpoint for that 🤔

@sesheta
Copy link
Member

sesheta commented Sep 17, 2022

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta sesheta closed this as completed Sep 17, 2022
@sesheta
Copy link
Member

sesheta commented Sep 17, 2022

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.

@VannTen
Copy link
Member

VannTen commented Sep 19, 2022 via email

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Sep 19, 2022
@codificat
Copy link
Member Author

/reopen

@sesheta
Copy link
Member

sesheta commented Sep 19, 2022

@codificat: Reopened this issue.

In response to this:

/reopen

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.

@sesheta sesheta reopened this Sep 19, 2022
@codificat codificat moved this to 🏗 In progress in Planning Board Sep 24, 2022
@Gkrumbach07 Gkrumbach07 moved this from 🏗 In progress to 📋 Backlog in Planning Board Sep 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Planning Board
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
4 participants
@goern @codificat @VannTen @sesheta