Migrate the default branch from master to main
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 1〜2日
- 初心者へのやさしさ
- 15/100
調査の方向性
This is an operational runbook, not a code change, and it needs maintainer access to the GitHub repository and the stemcell Concourse target. Read ci/pipeline.yml and ci/configure.sh to see where the source branch is pinned to master and where the bump-deps and publish jobs write. Done means the default branch is main, the usn-resource Git resource tracks main, and master is gone with the writing jobs restored to their prior state. Ask a maintainer before touching the live pipeline.
索引モデルが issue の本文から書いたものです。
説明
Native rename completed and verified on 2026-11-02T19:40:53.680049+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
09d4d6f519b9676b82e20e233e9bcd3df954ba8eis preserved onmain; repository contents are unchanged by the rename. masteris 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, pointsorigin/HEADatorigin/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 #24 is merged. The live usn-resource Git resource already used main at cutover; it was preserved. The dependency-update and publishing jobs were paused with no active writers, then restored to their original states after validation. The image remains bosh/usn-resource:latest.
Successful CI evidence: isolated check/fetch and actual pipeline resource check. Existing application tests continue through the normal pipeline; no release or dependency-update job was manually triggered for this 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.
- 主要言語
- Go
- スター
- 2
- フォーク
- 0
- 平均マージ
- 21時間 52分
- マージ済み PR(30日)
- 2
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
github/github-mcp-server#3865 ·
メンテナーはふだん 2 日以内に返信
-
kind/features
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
TencentBlueKing/bk-nodemgr#4017 ·
メンテナーはふだん 1 日以内に返信
-
ssa: wait errors drop the kstatus message, so health check failures don't say why対応中かも @schdief が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
equinor/radix-operator#2066 ·
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
microsoft/terraform-provider-msgraph#188 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信