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-crypt status in folders with many untracked files #293

Open
sroemer opened this issue Jun 13, 2023 · 4 comments
Open

git-crypt status in folders with many untracked files #293

sroemer opened this issue Jun 13, 2023 · 4 comments

Comments

@sroemer
Copy link

sroemer commented Jun 13, 2023

I am using git to keep track of my configuration files in a 'dotfiles' repository. In my case my home folder is a git repository on its own and the git configuration for this is configured with status.showuntrackedfiles=no. Obviously the home folder contains quite a large amount of files and git-crypt status tries to show a status for each of it which results in the status being quite unusable.

Wouldn't it be useful if git-crypt status also (maybe even optionally) respects the configuration accordingly or even only cares about tracked files at all? I currently don't see why someone would care in the status about untracked files, but maybe I am missing something here.

@sroemer
Copy link
Author

sroemer commented Oct 11, 2023

Additional note on that:

From the code I see that git-crypt status calls git ls-tree to get a list of files. For this operation the parameters -cotsz are used, with the -o causing ls-files to "show other (i.e. untracked) files in the output" (which is the description from the help page).

Here -ctsz should be enough to show all tracked files (including staged files). A manual test of calling git ls-tree -ctsz seems to work as expected on a first try.

@Aetf
Copy link

Aetf commented Nov 12, 2024

I'm in the same boat. Any chance we could get this fixed?

@rvsmooth
Copy link

I'm in the same boat. Any chance we could get this fixed?

same here...:)

@sroemer
Copy link
Author

sroemer commented Dec 6, 2024

Sadly I don't see any development going on here anymore, so unless AGWA hands over the project or someone creates a fork and continues to maintain it, I don't see that happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants