One command to rule them all

23 comments

fuck it. rm -rf repository; git clone repository

Been using git since almost as long as its been around, still can't be bothered to learn to how to fix conflicts.
- Rename it, so you can run diff on those surprising things that in no way could have changed, but are not equal to the repository. And then delete.
  
  Or keep the X-old; X-backup; X-bkp; X-old-old; X-old3 dirs.
mv .git .git_old7

git init

git add .

git commit -m "almost working"
- Lmao this is perfect
Neither remove untracked files sadly.
- git stash my friend
  
  I think git clean is more appropriate. With git stash you create a stash which you then have to drop.
- That's why I follow it with git clean -fd
git restore . ?
Or am I misinterpreting the problem?
- git restore is a pretty new command AFAIK. Those of us who learned git before its existence have probably stuck to the old ways of git reset --hard.
  
  Yep, I just learned of this command..
alias mybad='git add -u && git commit --amend --no-edit && git push --force-with-lease'
- 😂😂😂
And lose my untracked changes?

https://m.youtube.com/watch?v=guv5LUT1AFw&t=7s
git stash
That is stupid. Those commands are for different use cases.

23 comments