Migrate the default branch from master to main

Abierto
#25 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
15/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
docker, git, github, shell
Área
ci-cd, devops

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
2
Forks
0
Merge medio
21 h 52 min
PR fusionados (30 d)
2

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.