Explore >> Select a destination
|
You are here 
|
blog.fritzhardy.com | ||
| | | | |
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 [...] | |
| | | | |
sookocheff.com
|
|
| | | | | This is something I often do but rarely remember the steps for. This post is intended to serve as a reminder for me and anyone else having the same question: how to add an upstream remote git repository. Start by forking the repository you are contributing to and cloning that repository to your local file system. In this example, we will use the Elasticsearch repository and assume you have cloned it locally. | |
| | | | |
mikecoats.com
|
|
| | | | | A common time-saving 'hack' of mine when building 'new-but-related-to-old' projects is to fork an existing code base and use it as the boot-strap for the new project. GitHub, however, does not provide the functionality on their website to fork your own project; you can only fork other people's projects. Here's how to work around that. | |
| | | | |
haacked.com
|
|
| | | A git alias to clean up gone branches. Even ones that have been squashed and merged. | ||
