New repositories created by Copilot use `master` instead of `main`

Abierto
#4,041 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
64/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
git
Área
desktop, developer-experience

Línea de trabajo

Start by reproducing the issue in the GitHub Copilot app and inspect the repository-creation flow that initializes the local Git repository. Trace how the initial branch name is selected, then verify with git branch --show-current that creation uses main or the applicable configured default branch.

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

Descripción

triage
Short summary

When the GitHub Copilot app creates a new repository from scratch, it initializes the repository with master as the default branch instead of main.

Affected version or release

Current GitHub Copilot desktop app as of 2026-09-18 (exact build not captured).

Installation context

GitHub Copilot desktop app on macOS, creating a new local repository through a Copilot session.

What happened?

I asked the GitHub Copilot app to create a new repository. The resulting repository used master as its initial/default branch.

GitHub-hosted repositories have defaulted to main since 2020 unless a user, organization, or enterprise explicitly configures another name. The app appears to be relying on a local git init fallback or otherwise hard-coding/allowing master, rather than using main or honoring the applicable configured default branch name.

Steps to reproduce
  1. Open the GitHub Copilot app.
  2. Start from an empty folder or ask Copilot to create a new repository.
  3. Allow Copilot to initialize the Git repository.
  4. Inspect the initial branch name with git branch --show-current.
  5. Observe that the branch is named master.
Expected behavior

The initial branch should be named main, unless a different default branch name is explicitly configured for the user, organization, enterprise, or local Git environment. Ideally, repository creation should consistently honor the applicable configured default.

Additional context

GitHub's default-branch guidance states that new repositories created on GitHub use main: https://github.com/github/renaming#new-repositories-use-main-as-the-default-branch-name

Related but not duplicate reports:

  • #511 describes the app assuming master when calculating changes.
  • #786 describes collection projects not respecting per-repository default branches.
Lenguaje dominante
Sin datos de lenguaje
Estrellas
2.1k
Forks
157
Sin PR fusionados en 30 d

Guía de contribución

Abrir la guía de contribución

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.

Más de github/app

Todos los issues de github/app

Issues similares

Más issues de Desktop Dev

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.