More options for uncommitted changes#2222
Merged
Merged
Conversation
Member
Author
|
I am enjoying this in everyday usage. |
Contributor
|
Hey Hadley, this looks interesting! Wonder if you could fit in #2001 in the PR? I have been using usethis with my branch for a while now, and I really like being able to view which file is problematic, ignore or click on the files manually and look. It would show Uncommitted files (file1, file2, etc.) |
Do this like ui_yep(), which is a cli_inform + menu
jennybc
force-pushed
the
uncommited-options
branch
from
96981fb to
6097dbf
Compare
Member
|
@olivroy I'll still have a look at including some detail about the affected files. But I wanted to go ahead and take this improvement. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Fixes #1300
Currently 100% vibe coded. It seems straightforward enough, but I'm suspicious of the use of
on.exit()here (although it is a pragmatic way to avoid bigger API changes).