Explore >> Select a destination
|
You are here 
|
davidalfonso.es | ||
| | | | |
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 [...] | |
| | | | |
jo-m.ch
|
|
| | | | | Software Engineering Principles # Start simple and iterate, you won't get it right the first time anyways Make it fail gracefully There can never be enough logging, debug statements, asserts Measure before you optimize Make it hard to do the wrong thing Ugly hacks keep the world spinning Limitations are as important as features. Magic is bad Hyrums Law is very real and needs to actively worked against if you don't want to deal with it's fallout Specifications are important. If someone wants you to build something, it needs to be specified. Documents # Design and Decision # Should contain: | |
| | | | |
rick.cogley.info
|
|
| | | | | It's possible to update a forked git repository using the Terminal or one of the many good GUIs for git, but did you know Github gives you a way to update a fork directly in its web interface? | |
| | | | |
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. | ||
