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

Aperta
#4,041 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
64/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
git
Ambito
desktop, developer-experience

Direzione di ricerca

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.

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

Descrizione

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.
Lingua principale
Nessun dato sulla lingua
Stelle
2.1k
Fork
157
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Apri la guida per i contributori

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.

Altre issue di github/app

Tutte le issue di github/app

Issue simili

Altre issue su Desktop Dev

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.