- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 658
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
Feature Request: sort files by git status #1227
Comments
Oh that could be super useful! I propose Design ThoughtsMatching the order of
So I propose to sort by like this:
Sorting staged-changes before no-staged-changes also matches a decision already made in $ exa --long --git
Permissions Size User Date Modified Git Name
.rw-r--r-- 155 ben 25 Nov 17:23 NM unselectable.scss
.rw-r--r-- 612 ben 24 Nov 16:04 M- media.scss
.rw-r--r-- 260 ben 25 Nov 17:23 -M icon.scss
.rw-r--r-- 59 ben 25 Nov 17:23 -N plain-link.scss
.rw-r--r-- 96 ben 21 Nov 14:20 -- hoverable.scss Which corresponds to: $ git status
Your branch is up to date with 'origin/main'.
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
modified: media.scss
new file: unselectable.scss
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: icon.scss
modified: unselectable.scss
Untracked files:
(use "git add <file>..." to include in what will be committed)
plain-link.scss P.S. a third reason for making has-staged-changes versus does-not-have-staged-changes as the primary sort is that right before a commit, the most important/salient difference is what's staged - and any deliberate use of the staging area (staging smaller pieces for individual commits instead of basically ignoring the staged/unstaged difference and committing all outstanging changes at once), it's really helpful to have a fast-and-easy-to-visually-parse cue of staged-vs-unstaged. |
Sounds excellent to me. |
Would it be possible to add a feature to sort files in a repo by their git status?
The text was updated successfully, but these errors were encountered: