Migrate the default branch from master to main
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 8/100
- Tipo di issue
- Refactoring
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- git, github
- Ambito
- build-system, devops
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
2fa1e1cc2dc66cda6f58f09f38f256bffa507770is 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 #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.
- Lingua principale
- Ruby
- Stelle
- 2
- Fork
- 6
- Merge medio
- 1g 19h
- PR unite (30g)
- 1
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Issue simili
-
Bug Ruby
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
getsentry/sentry-ruby#3211 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
internetee/registry#2984 ·
I maintainer di solito rispondono entro 6 giorni
-
interest-zsv
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
hitobito/hitobito_zsv#6 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
ecosyste-ms/issues#862 ·
I maintainer di solito rispondono entro 1 giorno
-
Redis Lua error `@user_script:52: ERR value is not an integer or out of range` when `window_size` is configuredForse già presa @mimosa l’ha presa oggi. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno