Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Git: branches no longer sorted by commit date #80045

Closed
bpasero opened this issue Aug 29, 2019 · 1 comment · Fixed by #80096
Closed

Git: branches no longer sorted by commit date #80045

bpasero opened this issue Aug 29, 2019 · 1 comment · Fixed by #80096
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release git GIT issues verified Verification succeeded
Milestone

Comments

@bpasero
Copy link
Member

bpasero commented Aug 29, 2019

Steps to Reproduce:

  1. have a couple of branches
  2. click on the branch picker

=> 🐛 the branches are no longer sorted by commit date

This works fine in stable, so seems like a regression.

INSIDERS
image

STABLE
image

(my git version is 2.23.0)

@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug git GIT issues labels Aug 29, 2019
@joaomoreno
Copy link
Member

Stable:

git for-each-ref --format %(refname) %(objectname) --sort -committerdate

Insiders:

> git for-each-ref --format %(refname) %(objectname) --sort committerdate

Yup, there's a - missing.

@joaomoreno joaomoreno added this to the August 2019 milestone Aug 30, 2019
@alexdima alexdima added the candidate Issue identified as probable candidate for fixing in the next release label Aug 30, 2019
@aeschli aeschli added the verified Verification succeeded label Aug 30, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release git GIT issues verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants