Explore >> Select a destination
|
You are here 
|
rick.cogley.info | ||
| | | | |
jinyuz.dev
|
|
| | | | | There was a pull request on GitHub and it contains a feature I wanted to test. I didn't know how to test it locally. Should I just copy the changes to my local since the changes weren't that big? But what if it was? Luckily, I found some answers by googling and decided to write it up for future reference. Git provides a command for it and here is the sample syntax | |
| | | | |
blog.thms.uk
|
|
| | | | | If you have forked an open source project you sometimes want to apply changes from another fork to your own. This post shows how to merge branches from another fork using either GitHub or the command line. | |
| | | | |
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: | |
| | | | |
www.maxpou.fr
|
|
| | | A Git Cheat Sheet that focuses on Essential Commands for Experienced Developers. | ||
