-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
git fresh-branch deletes everything without asking. #142
Comments
probably not, you can always |
yep but I was in a really dirty state :/ Kilian C. On Monday, October 15, 2012 at 3:55 PM, Arian Stolwijk wrote:
|
just checkout master again, it's not gone |
I had uncommitted changes, they are gone. Kilian C. On Monday, October 15, 2012 at 6:53 PM, TJ Holowaychuk wrote:
|
so you didn't commit in two days? |
yep, same unfinished ticket, I know that's unusual/wrong and I am not complaining about that. I just thought that it would be nice to have some sort of warning. It deletes untracked files too...Kilian C. On Monday, October 15, 2012 at 7:41 PM, TJ Holowaychuk wrote:
|
i'd like to remove this command all-together personally but a warning would definitely be nice |
git-fresh-branch: Check for changes and prompt for input before nuking. (Issue: #142)
git-fresh-branch: Check for changes and prompt for input before nuking. (Issue: tj#142)
I just lost 2 days of work.
The text was updated successfully, but these errors were encountered: