Microsoft/vscode

Git - Branch on new local repo fails

Open

#200,773 opened on Dec 13, 2023

View on GitHub
 (1 comment) (0 reactions) (1 assignee)TypeScript (10,221 forks)batch import
buggithelp wanted

Repository metrics

Stars
 (74,848 stars)
PR merge metrics
 (Avg merge 11h 43m) (1,000 merged PRs in 30d)

Description

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.85.0 (user setup) commit af28b32d7
  • OS Version: Windows_NT x64 10.0.22621

Steps to Reproduce:

  1. Create new folder and enter folder: mkdir test1 && cd test1

  2. Open vscode: `code . --disable-extensions

  3. Use activity bar to initialize new repo

  4. Create new text file but don't check it in

  5. Use command palette to create new branch Git: Create Branch with name test

  6. Get error - "Error: Git: fatal: Head is not a commit and a branch test cannot be created from it"

    image

  7. Show git command:

    > git checkout -q -b test --no-track HEAD
fatal: 'HEAD' is not a commit and a branch 'test' cannot be created from it

  8. Reproduce branch in terminal: git checkout -b test => success

    image

Contributor guide

Research direction
Investigate the VS Code Git extension's branch creation logic. The command `git checkout q b test no track HEAD` fails when HEAD is not a commit. Compare with `git checkout b test` which works. Trace the code path in extension/git/src/git.ts or similar to see why it uses ` no track HEAD` instead of just ` b test`.
Tech stack
typescript
Domain
developer experiencetooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65