/explore
|
You are here |
8yd.no | ||
| | | | |
blog.tracefunc.com
Just a random coder writing about technology, web development, and various other geeky topics. |
|
| | | | | ||
| | | | |
mislav.net
How to settle on whether to merge or rebase at specific points in a team-shared git workflow. |
|
| | | | | ||
| | | | |
felixrieseberg.com
You need to rebase a feature branch you worked on weeks ago. Merge conflicts everywhere. But: There's hope. Use "git merge --squash". |
|
| | | | | ||
| | | | |
citizen428.net
I originally wrote this article for Codementor in October 2014. It should have something for everyone, from fairly new git users to experienced developers. 1. Discard local file modifications Sometimes the best way to get a feel for a problem is diving in and playing around with the code. Unfortunately, the changes made in the process sometimes turn out to be less than optimal, in which case reverting the file to its original state can be the fastest and easiest solution: |
|
| | | |||