Migrate the default branch from master to main

Aperta
#25 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
15/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
docker, git, github, shell
Ambito
ci-cd, devops

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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 09d4d6f519b9676b82e20e233e9bcd3df954ba8e 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 #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.

Lingua principale
Go
Stelle
2
Fork
0
Merge medio
21h 52m
PR unite (30g)
2

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

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.