This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Bolding file name if it’s not staged. #955
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Could someone take a look here? |
|
this is awesome. any updates? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in these issues across Atom repositories:
I found it difficult to choose a new color schema to identify unstaged files (atom/one-light-ui@6a0f4d9) so I’ve just bolded the filename to identify files not staged yet.
I maintain a plugin called atom-hg and my
isStatusStagedmethod is already exposed. There’s a method with the same name in git-utils but it doesn’t seem to be exposed yet so I manually added the same verification as a fallback ((status & 15) > 0).It would help a lot because we’ll finally have a clue whether a file is staged or not.