Migrate the default branch from master to main

未关闭
#16 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
1-2 天
新手友好度
8/100
Issue 类型
重构
描述清晰度
描述清楚
活跃度
活跃
技术栈
git, github

调研方向

This is a maintainer runbook, not a code change. Read ci/pipeline.yml and ci/configure.sh to see where the bosh-cpi-ruby-gem source branch is set, and check lib/cloud/errors.rb for the link the checklist verifies. The GDC comment reference is in bosh-gdc-cpi-release/bosh-cpi/pkg/bosherr/bosherr.go. Done means the checklist items are verified by a maintainer with pipeline and repository access, which a newcomer cannot perform.

由索引模型根据 Issue 内容生成。

描述

Native rename completed and verified on 2026-11-02T19:40:59.480729+00:00. This repository now defaults to protected main.

The remaining configuration step is to merge community PR #1675, now ready after all four branch renames were verified.

Verified results:

  • Original tip 2fa1e1cc2dc66cda6f58f09f38f256bffa507770 is preserved on main; repository contents are unchanged by the rename.
  • master is absent. Every other branch and tag matches the immediate pre-rename snapshot.
  • Branch protection is identical apart from the branch name. No rulesets or open PRs needed retargeting.
  • A fresh clone selects main, points origin/HEAD at origin/main, and checks out the preserved tip.
  • GitHub-visible webhook IDs/events/activation and CodeQL default-setup settings are preserved; no webhook branch configuration was found. External-service backend settings were not queried.

Pipeline PR #15 is merged. The live bosh-cpi-ruby-gem Git resource changed from master to main; all other pipeline configuration is identical. The separate semver branch/resource and release tags are preserved. Publishing jobs were paused with no active writers, then restored to their original states after validation.

Successful CI evidence: isolated check/fetch, actual pipeline resource check, and the unit-test build running at cutover. No gem release was triggered to test the migration.

GDC PR #16 is ready; its new main comment-link destination resolves. This comment-only follow-up does not gate the migration.

Checklist:

  • Refresh source and pipeline consumer audit and capture preflight state.
  • Prepare/merge required source changes and coordinate writing jobs where applicable.
  • Perform native rename; verify tip, protections, refs, integrations, and fresh cloning.
  • Verify actual resource checks and isolated read-only fetches against the renamed default.
  • Restore original pipeline/job pause states where applicable.
  • Make community PR #1675 ready after all four migrations were verified.
  • Merge community PR #1675.

Peribolos synchronization is asynchronous. Continue without waiting for a particular run; a later successful synchronization including the merged community configuration must still finish before the org configuration is fully applied. This is a completion note rather than a per-run checklist gate.

Rollback if needed: preserve the current tip; pause/drain writing jobs where applicable, use GitHub's native rename back to master, restore the prior pipeline branch setting, and coordinate reverting the community setting if merged. Recheck refs and protections before restoring original pause states. Do not create a divergent compatibility branch.

主要语言
Ruby
星标
2
派生
6
平均合并
1 天 19 小时
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。