Learn Git Branching VS Gitless

That’s amazing, will definitely use this in teaching. Would be cool if this could also be compiled for the web/WASM. Also, another git game / tool I had good experiences with is https://learngitbranching.js.org/. - Source: Hacker News / 26 days ago

Learning Git can be more fun with interactive games and challenges. Check out sites like Git Games (https://gitgames.io/) and Git Branching (https://learngitbranching.js.org/) for a gamified approach to mastering Git concepts. - Source: dev.to / about 2 months ago

Learn Git Branching: Interactive Git tutorial allows you to experiment with Git commands in a simulated environment, providing a hands-on learning experience. - Source: dev.to / about 2 months ago

> I still can't accomplish anything more than the most basic things... A few hours on https://learngitbranching.js.org/ and it'll make sense to you. - Source: Hacker News / 3 months ago

Pull Requests (or Merge Requests) are merged only when (1) all of the automated tests pass; and (2) enough necessary reviewers have indicated approval. Git doesn't tell you when it's necessary to have full test coverage and manual infosec review in development cycles that produce releases, and neither do Pull Requests. https://westurner.github.io/hnlog/#comment-19552164 ctrl-f hubflow It looks like datasift's... - Source: Hacker News / 4 months ago

One such project is the Gitless initiative which has a Python wrapper around Git proper providing far-simpler workflows based on some solid research. Unfortunately it doesn't look like Gitless' Python codebase has had active development recently, which doesn't inspire much confidence. - Source: dev.to / almost 2 years ago

You and me both. Git's interface has been very hard for me to understand (especially coming from Mercurial). I ended up finding Gitless (https://gitless.com), a wrapper around Git with a better interface, and loving it. - Source: Hacker News / almost 2 years ago

> > To differentiate from Git Pijul should focus on usability... If Pijul has an easy to use interface like Mercurial did then that will massively help adoption. > I don't think the goal or differentiation of pijul is to be popular via good UI, though. If the theory of patches is good, it doesn't matter if pijul "wins" or not, as long as whatever does can integrate it. If the theory of patches is bad, I... - Source: Hacker News / over 2 years ago

I'd like to think it was my project (https://github.com/martinvonz/jj), but other possibilities include Gitless (https://gitless.com/) or Bazaar (https://bazaar.canonical.com/). - Source: Hacker News / over 2 years ago

Gitless [1] has already been mentioned in another comment here. [2] That makes it easier to use hit for those who are not as experienced or haven’t learned about the internals of git. For a different model (and other types of workflows), consider Fossil SCM. [3] Here’s a comparison of fossil with git, and what these tools are a good fit for. [4] I found fossil easier to understand, relatively speaking, and it... - Source: Hacker News / over 2 years ago