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: support not passing -u to git status for large repositories #140755

Closed
brianduff opened this issue Jan 15, 2022 · 4 comments
Closed

Git: support not passing -u to git status for large repositories #140755

brianduff opened this issue Jan 15, 2022 · 4 comments
Assignees
Labels
feature-request Request for new features or functionality git GIT issues verification-needed Verification of issue is requested verified Verification succeeded
Milestone

Comments

@brianduff
Copy link

For very large git repositories, the -u option (an alias for -uall) can sometimes make git status take a large amount of time and CPU.

Would like to have an option (off by default) to ignore individual files in untracked directories, which is the default behavior of git status with no arguments (equivalent to -unormal).

@brianduff brianduff changed the title Git: support not passing -u for large repositories Git: support not passing -u to git status for large repositories Jan 15, 2022
brianduff added a commit to brianduff/vscode that referenced this issue Jan 15, 2022
This option is off by default. When switched on, it avoids passing the
`-u` option to `git status`, which can be significantly faster on huge
repos with the caveat that files in untracked directories will no longer
show as untracked files.
@lszomoru lszomoru added git GIT issues feature-request Request for new features or functionality labels Jan 15, 2022
@lszomoru
Copy link
Member

Fixed with 29f9e51.
Though for the record, I am also looking at this pull request - #136698

@lszomoru lszomoru modified the milestones: Backlog, April 2022 Mar 29, 2022
@joyceerhl joyceerhl added the verification-needed Verification of issue is requested label Apr 25, 2022
@lszomoru
Copy link
Member

Verification steps:

  • Launch VS Code, and open a folder/workspace that contains a git repository
  • Open the Git output using the Git: Show Git Output command
  • Switch to the "Source Control" viewlet, and press the action to "Refresh" the list of changes
  • Look at the Git output and confirm that you see a git status -z -uall command being executed
  • Open Settings and set the git.untrackedChanges setting to hidden
  • Switch to the "Source Control" viewlet, and press the action to "Refresh" the list of changes
  • Look at the Git output and confirm that you see a git status -z -uno command being executed

@rzhao271 rzhao271 added the verified Verification succeeded label Apr 27, 2022
@github-actions github-actions bot locked and limited conversation to collaborators May 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality git GIT issues verification-needed Verification of issue is requested verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants
@brianduff @lszomoru @rzhao271 @joyceerhl and others