A colleague encountered a problem on git that piqued my curiosity. He had a file that was already tracked in git. When he modified it in his IDE, it didn’t list it in the modified files to add to the next commit. And even when editing it in a simple code editor and checking the state of the local repository with the command line, git didn’t see the changes.
What if git could help us detect code smells? I’m going to share with you a past experience that resurfaced through a tweet.
This week, I’m going to share with you a git command that illustrates my dark side as a developer. So hang on tight!
As the cleanup of the git repository wasn’t complete, I had to check the changes I was making, understand the differences between branches or check that the rebasing of a branch gave the same result despite many conflicts.
Continue reading →If there’s one universal tool for developers, it’s git. Indeed, this decentralized version manager (SCM for Source Code Management) has become a must-have over the years.
Continue reading →This week, I had to clean up a git repository that had aged badly.