Explore >> Select a destination
|
You are here 
|
thork.net | ||
| | | | |
pbrisbin.com
|
|
| | | | | Git submodules are pretty great. They allow you to have nested git repositories so that modular parts of your app can exist as separate repos but be worked with as one file tree. Another benefit is that when submodules are pushed to github they appear simply as links to the repos they represent. If your not familiar, go ahead and google then come back - how submodules work overall is not the point of this post. | |
| | | | |
techtldr.com
|
|
| | | | | Here are the steps that I too to merge multiple GitHub repos into one, while preserving all commit history. The process took about 30 minutes for 5 repos. As a result, I feel like my GitHub page is cleaner and code is actually better organized and easier to find. TLDR: Create new repo (or use [...] | |
| | | | |
sporks.space
|
|
| | | | | Let's say you have a submodule that you want to change, but the submodule itself is huge. You might not want another copy of it, so you're holding off on running git submodule update --init. Internally in your repo, Git... Continue reading ? | |
| | | | |
hiltmon.com
|
|
| | | |||
