Skip to content

Migrate to new default branch name #50

@spiffxp

Description

@spiffxp

Part of umbrella issue to rename default branches: kubernetes/org#2222

Copy-pasted checklist from https://raw.githubusercontent.com/kubernetes/community/master/github-management/default-branch-migration.md

Changes pre-rename

Make the following changes before renaming the branch the master branch.

Note: There might be additional changes required that have not been
covered in this checklist.

Anytime

These changes are non-disruptive and can be made anytime before
renaming the branch.

Just before rename

These changes are disruptive and should be made just before
renaming the branch.

  • If a prowjob mentions the master branch in base_ref,
    update it to the main branch. For a periodic job, ensure that
    the branch is renamed between periodic job runs.

    • n/a - no jobs do this
  • If a prowjob mentions master in its name, rename the job to
    to not include the branch name. [status-reconciler] should automatically
    migrate the PR status contexts to the new job name but this has not been tested yet.
    The job with the new name will also appear as a differt job in Testgrid.

    • n/a - no slack-infra jobs do this
  • If a prowjob calls scripts or code in your repo that explicitly
    reference master, update all references to use main.

  • If the repo has netlify configured for it, ask a member of the GitHub
    Management Team to rename the master branch to main in the netlify site config.
    It can't be controlled through the netlify config in the repo.

    • n/a - no netlify

Approval

  • Once all non-disruptive tasks have been completed and disruptive tasks
    have been identified, assign the GitHub Management team ([@kubernetes/owners])
    for approval.
    • verbally asked during github management meeting

Rename the default branch

Changes post-rename

After the default branch has been renamed to main, make the following
changes.

Note: There might be additional changes required that have not been
covered in this checklist.

Prowjobs

Prow config

  • If the [milestone_applier] prow config references the master branch,
    remove it from the config.

    • n/a
  • If the [branch_protection] prow config references the master branch,
    remove it from the config.

    • n/a

Other

/assign
/sig contributor-experience
/kind cleanup

Metadata

Metadata

Assignees

Labels

kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions