Only update files if work-tree changes #535
Open
Conversation
This file contains hidden or 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
Git commands that don't modify the work tree don't trigger yadm updates E.g. running `yadm status` doesn't update any alt files
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Git commands that don't modify the work tree don't trigger yadm updates
E.g. running
yadm statusdoesn't update any alt filesWhat does this PR do?
My alt files got reloaded with every git command. So I searched for the reason and found the open TODO and tried to fix it.
I'm not perfectly familiar with bash syntax, so I'll happily implement any suggetions :)
What issues does this PR fix or reference?
#355
Previous Behavior
Every time you did any git command (e.g. git status) all of the alt files got reloaded
New Behavior
Only git commands that change the work tree reload any files.
Have [tests][1] been written for this change?
No
Have these commits been [signed with GnuPG][2]?
Yes