Darcs [0] patch theory was a predecessor to OTs/CRDTs (and a predecessor to git as well; in some ways it is the "smart" to which git was named "dumb"). When it works and performs well it is still sometimes version control magic. Pijul [1] is an interesting experiment to watch, trying to keep the patch theory flag flying and also trying to bring in updates from OTs and CRDTs as it can. [0] https://darcs.net [1]... - Source: Hacker News / 5 months ago

Perforce. As for DVCS, the best one I've used is Darcs: https://darcs.net/ There are some sticky wickets (specifically, exponential-time conflict resolution) that hindered its adoption. Thankfully, there's Pijul, which is like Darcs but a) solves that problem; and b) is written in Rust! The perfect DVCS, probably! https://pijul.org/. - Source: Hacker News / 6 months ago

Well technically one alternative I am going to bring up predates Git by several years, and that's DARCS. Fans of DARCS have written plenty of material on Git's perceived weaknesses. While DARCS' Haskell codebase apparently had some issues, its underlying "change" semantics have remained influential. For example, Pijul is a Rust-based contender currently in beta. It embraces a huge number of the paradigms,... - Source: dev.to / almost 2 years ago

We already have the "haskell of version control", darcs, i.e. Nobody uses it. Source: over 2 years ago

Use hub here via CLI and forget the gui https://hub.github.com/. - Source: Hacker News / 9 months ago

Try automating the PR process as much as possible. Make use of tools like hub CLI for speeding up the pull request process. Code quality tools can help you automate the due diligence for coding standards and conventions, and test automation tools can assist in bug discovery, and identifying security vulnerabilities. - Source: dev.to / 12 months ago

Parse_git_branch() { # Speed up opening up a new terminal tab by not # checking `$HOME` ...which can't be a repo anyway # # For the heck of it, micro-optimize this too: # time (repeat 1000000 { [ "$PWD" = "$HOME" ] } ) == ~4.2s # time (repeat 1000000 { [[ "$PWD" == "$HOME" ]] } ) == ~1.4s [[ "$PWD" == "$HOME" ]] && return # Fastest known way to check the current branch name ... Source: almost 2 years ago

You can always query via github api or use the hub client (from their home page https://hub.github.com/). Source: over 2 years ago