/explore
|
You are here 
|
etodd.io | ||
| | | | |
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. | |
| | | | |
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. | |
| | | | |
endot.org
|
|
| | | | | I've been using git_backup to back up the websites I run for quite a while now. It works well and I only need to scan the daily cron emails to see if the backup went well or if there were any odd files changed the day before. One thing that I didn't expect when I started using it was how it would enable developing those websites in a sandbox without any danger of affecting the production instances. | |
| | | | |
unixdigest.com
|
|
| | | [AI summary] This tutorial explains a simple Git workflow to manage your home directory by using a white-listing approach with a wildcard in .gitignore to selectively track specific files while ignoring everything else. | ||
