/explore
|
You are here 
|
v5.chriskrycho.com | ||
| | | | |
zerowidth.com
|
|
| | | | | How Jujutsu's flexibility and safety changed my approach to version control. | |
| | | | |
kubamartin.com
|
|
| | | | | Jujutsu (jj), a new version control system written in Rust, has popped up on my radar a few times over the past year. Looked interesting based on a cursory look, but being actually pretty satisfied with Git, and not having major problems with it, I haven't checked it out. That is, until last week, when I finally decided to give it a go! I dived into a couple blog posts for a few of hours, and surprisingly (noting that we're talking about a VCS) I found myself enjoying it a lot, seeing the consistent design, and overall simplicity it managed to achieve. | |
| | | | |
github.com
|
|
| | | | | A Git-compatible VCS that is both simple and powerful - jj-vcs/jj | |
| | | | |
blog.oddbit.com
|
|
| | | Always work on a branch (never commit on master) When working with an upstream codebase, always make your changes on a feature branch rather than your local master branch. This will make it easier to keep your local master branch current with respect to upstream, and can help avoid situations in which you accidentally overwrite your local changes or introduce unnecessary merge commits into your history. Rebase instead of merge If you need to incorporate changes from the upstream master branch in the feat... | ||
