π©Ί Doctors have stethoscopes.
π§ Mechanics have spanners.
π¨βπ» We developers, have Git.
Have you noticed that Git is so integral to working with code...
For further actions, you may consider blocking this person and/or reporting abuse
I like a clean commit history, interactive rebasing was a real find for me!
Great post! The section on common Git commands resonated with me. CommandGit app builds on this foundation by letting users execute these commands in batches, making complex workflows simpler without hiding the command line magic.
Good article, as audience for such article is intended for git newcomers. I would have suggest to use
--force-with-leasein your example instead of--forceand explain the differences.That does actually make sense I will update the article shortly! Thanks for pointing that out
I found back the article I wrote about it ages ago
my git aliases: please = git force --with-lease
Christophe Colombier γ» Aug 10 '22
I have used git extensively throughout the majority of my 23 year career. One thing I tell newcomers is to not be afraid of the command line, but donβt feel inadequate if you use guis. GitHub desktop is a great application, especially for viewing commit contents and diffs. I use it every day along with the command line. Try it out. I also ask newcomers to make a PR on their first or second day, even just a readme fix, so they understand the process
Great post ! I would add that you can make your life easier when conflicts happen with
git mergetool, which can be configured to your favorite file comparator. I personnaly use p4merge that I find quite clear to use πsuper cool @awenath I was unaware of those tool. Will check them out for sure
Wonderful contribution! I found the part about familiar Git commands particularly impactful. The CommandGit application enhances this concept by enabling users to perform these commands in groups, streamlining intricate processes while still preserving the essence of command line mastery.
This is awesome!
Awesome....very interesting and knowledgeable topics all you are mentioned
Great post ! I had to look what's the difference between
git switchandgit checkoutππGood stuff! I'm using git every day, but there is always something new you can learn. This is a nice cheat sheet to keep close.
How did I git anything done before without this?
badumdum
thanks for sharing
Excellent post!!
Nice illustrations, especially the one just under "Getting Started with Git".
hahah that the only one that is not mine, the original creator of the image has been linked to the image.
Awesome , great information
Good job!
Great post!
Thank you.
Skill learned: Rebase
Super helpful!
Nice article! Thanks
For the Peter's gif alone, worth the post the save for later
I see myself coming back to this.
Thanks, clear figures showing how git works
nothing good like a clean commit history
This guide has the potential to be incredibly valuable, providing clarity and insights to others who may be in a similar position. gold365
The best GIT write up ever!!!
The ultimate roadmap for mastering Git - wish I had this from day one! Lotus 365 In
You git it! Great read! Informative, humorous, and well written. Thanks for sharing!
Much appreciated @qyrusai !
Great explanation. The only change I'd make is to ditch the credential.helper section and replace it with the equivalent for ssh key. Nice to know about the different philosophies of branch management (Git Workflows). I typically use Pull Request workflow.
Thanks for that @rodkey makes sense. ssh is best practice for sure. Will update over weekend. Thanks for the input
Thank you for sharing, nice work for newbies π
You differentiate feature branch mode and PR mode, but they are the same from a git workflow perspective (or you did not explain how they are different).
And trunk-based-development is rarely commiting directly to trunk.
Keep up the good work π
Hey @bcouetil you are right to bring the similarity of both branching workflows in the article. Initially I included the PR workflow as well as the Feature branch work flow, because I read elsewhere that some smaller team with more liberal merging practices would merge without a PR. But to be honest since this is not an common ocurrance I think it makes sense to remove the PR workflow and explain that Feature branching merges by raising PRs. Cheers!
Hello. Thank you for publishing this great article! I am still working on reading through the guide but wanted to bring something to your attention. I am using Visual Studio 2022 and my Git is already connected to a repo with my own branch that has unstaged changes. I followed some of your sample commands in the "working with branches" section such as this:
# Will show the changes in the local repositorygit branch
However, for me, doing
git branchdoes not show the changes in the local repo. It simply shows me the branches available on my local machine (master, and pbi/123456).Doing
git statusis what shows me the changes in my branch. Not sure if I am just misunderstanding or if your comment needs modified. I mean no disrespect and I appreciate your content!You are right yeah,
git statusis what you run to see the status of the progression of your workflow, for example if the output is red, the unstaged changes have been detected, if the output is green/yellow (sorry I'm color blind and have an issue with those two) the changes have been stages (withgit add) and ready to committed.Git branches is only for viewing the available local branches. Sorry if that wasn't clear.
Nice blog @jakepage91 π
Cheers Ankur!
I wish I had this in the past... π
That Peter Griffin reference is sooo appropriate for how I feel about GIT. Thank you for an excellent overview of GIT, it helped me a lot.