I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
Thanks for sharing. I rarely use git rm - I usually use rm and commit. And I rename the path to something else if I need to keep it.
I added to my notes regarding cached and -r flags though.
I don't need to use git branch for a new branch. Your usage of git checkout -b is much more common and practical.
And pro tip. I rarely use add if a file already exists...
If i make file changes, then i do this for the directory (or use a dir name).
git commit .
You can also check the comments in your commit message editor window if you need to see which paths are going to be committed. Or use git status before you commit.
Here I commit changes to package.json and package-lock.json without using add but preventing changes in other files getting commited.
Passionate about education, fintech, Python, Javascript, progressive growth, and full-stack development.
Sometimes I write code, sometimes I just write.
Thanks for sharing. I rarely use
git rm- I usually usermand commit. And I rename the path to something else if I need to keep it.I added to my notes regarding cached and -r flags though.
I don't need to use
git branchfor a new branch. Your usage ofgit checkout -bis much more common and practical.And pro tip. I rarely use
addif a file already exists...If i make file changes, then i do this for the directory (or use a dir name).
You can also check the comments in your commit message editor window if you need to see which paths are going to be committed. Or use
git statusbefore you commit.Here I commit changes to package.json and package-lock.json without using
addbut preventing changes in other files getting commited.this is a new way of looking at things. Really helpful. Thanks Mike.