Disclaimer: Based on Google Gemini-Pro prompts! Let’s face it—the default git log output is a massive wall of plain text that is painful to scan. When you are working with a team, tracking down who did what and when can feel like reading a raw terminal dump. Today, we are going to fix that. We will transform your Git log into an interactive, beautifully structured, and color-coded masterpiece tailored specifically for your terminal workspace....
Disclaimer: Based on Google Gemini-Pro prompts! Managing version numbers can get messy when working solo. If you accidentally created development branches named after version numbers (like v0.1.0) or mixed up your tag formats, you can easily clean up your history and establish a friction-free release workflow. The Goal Convert version branches into permanent Git tags, format historical versions cleanly (v0.0.1 instead of v0.1), and establish a streamlined process for future releases....
First, analyze the git storage in the directory with: git filter-repo --analyze Then the large files can be removed from git history using git filter-repo as follows: git filter-repo --strip-blobs-bigger-than 10M This removes all files larger than 10MB from .git/objects/ directory. You may have to use --force argument, if the repository is not a fresh clone. The command will also remove the origin remote, so you will need to readd it!...
Problems I have encountered using Dropbox: Dropbox storage space available for use is really low, and is consumed relatively easily because of the .git folder. Dropbox real time sync has issues with git if multiple computers work on a project simultaneously. Although, it has been rare that I have encountere this. My current solution for this problem is as follows: Move the most space consuming .git folders outside of Dropbox. This way Dropbox won’t be syncing these large folders....
In the name of sheer simplicity, it would be advised to best not use the git submodule utility ! If there is the utmost need to have one directory within the other, then try to have only git repository among them, yeah. Or else, try to separate out the repositories into separate folders, yah ! It may happen that you may not be able to see new changes in the main directory after using submodule for a while....