stash: handle clean workspace on push() #214
Merged
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
pmrowla
force-pushed
the
stash-no-changes
branch
3 times, most recently
from
8e2e453 to
2df703d
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #214 +/- ##
==========================================
+ Coverage 82.35% 82.41% +0.06%
==========================================
Files 25 25
Lines 3559 3572 +13
Branches 622 626 +4
==========================================
+ Hits 2931 2944 +13
+ Misses 532 531 -1
- Partials 96 97 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
pmrowla
force-pushed
the
stash-no-changes
branch
4 times, most recently
from
8ab5ed6 to
f752282
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #211
is_dirtyorstatus, the check is done within the same backend, which eliminates inconsistencies when mixing status + stash calls across different backends(This PR does not address the lack of gitattributes support in dulwich)