/explore
|
You are here 
|
blog.cy.md | ||
| | | | |
ericlathrop.com
|
|
| | | | | One of my favorite parts of Git is how it lets you fix your mistakes. One mistake I needed to fix a few times in the last year was having two separate repositories, when they ought to be a single respository. I will present commands to merge a child repository into a parent respository as a subdirectory. The new child repository subdirectory will preserve its history and look like it was always part of the parent repository. | |
| | | | |
zzamboni.org
|
|
| | | | | I needed to copy a directory between two git repositories while preserving its history. I found some good instructions at http://gbayer.com/development/moving-files-from-one-git-repository-to-another-preserving-history/, which got me started, but I figured out a way to avoid having to move all the files into their directory again (lines 5-6 in Greg's instructions) by reversing the filter to remove everything I don't want instead of only including the directory I want. Here are the steps (the idea is the ... | |
| | | | |
cullmann.io
|
|
| | | | | Today I did run again into an old problem: You need to archive a lot small and large files inside a single Git repository and you have no support for Git LFS available. You did this several year and now you ended up in a state where cloning and working with the repository is unbearable slow. What now? Last time I did run into that, I archived the overfull repository to some "rest in peace" space and used git filter-branch to filter out no longer needed and too large objects from a repository copy that then will replace the old one for daily use. | |
| | | | |
bengarvey.com
|
|
| | | [AI summary] A practical guide to a simplified, safe workflow for managing version control with Git. | ||
