User-Friendly
Gitless aims to provide a simpler interface compared to Git, which can be beneficial for users who find Git's command-line interface complex and intimidating.
Simplified Workflow
Gitless simplifies branching and merging operations, reducing the cognitive load on developers who are overwhelmed by Git's more intricate command structure.
Improved Usability
By abstracting some of the more complex aspects of Git, Gitless improves usability, especially for beginners who struggle with Git's steep learning curve.
Fault Isolation
Gitless is built on top of Git, ensuring that users can still benefit from Git's robust version control features and data integrity mechanisms while enjoying a simplified experience.
This is unrelated to the tool called "Gitless": https://gitless.com/. - Source: dev.to / 14 days 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 3 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 3 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 3 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 3 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 3 years ago
People might be interested in gitless [0], which purports to be "a Git-compatible version control system, that is easy to learn and use". It appears to be built on top of git, using a simplified conceptual model. I read about it in one of Adrian Colyer's "the morning paper" blog posts from 2016, "What’s wrong with Git? A conceptual design analysis" [1], which summarizes the paper that critiques git and describes... - Source: Hacker News / over 3 years ago
You may like GitLess, it uses git under the hood, but has a simplified CLI: https://gitless.com/. - Source: Hacker News / over 3 years ago
Gl commit -p allows you to interactively commit parts of files. Gl doesn't take any abilities away (it's just git under the hood after all), it just exposes the abilities in sane ways. If you actually look at the homepage of gitless you will also immediately see what fuse does: https://gitless.com/#gl-fuse I believe that by reading that one, not very long page, most people (including non-programmers) can use gl... - Source: Hacker News / over 3 years ago
I think it's the other way around. The fact that git does not provide a clean analogous way to intuitively interact with it just demonstrates that the git interface is horribly broken. This is not essential complexity, it's just bad design that stuck. Take a look at https://gitless.com/ If you just look at a summary of the commands, you will have an accurate mental model of what's going on:- Source: Hacker News / over 3 years agogl init...
Something like gitless? https://gitless.com. Source: over 3 years ago
How should one go about achieving a 'decent fundamental understanding' (specific pointers, if you have them). And, how much time must one devote to being a 'good enough git guru'? (and, it surprises me that gitless is not more popular: https://gitless.com/ ). - Source: Hacker News / over 3 years ago
We took inspiration from gitless - "a Git-compatible version control system, that is easy to learn and use" - a project which works on top of Git and attempts to make it more intuitive. Check it out! Source: almost 4 years ago
I agree that collaborative text editing between multiple users simultaneously is hard. That doesn't mean that Git couldn't have a much better UI for this problem than it does. And while I agree that Git seems to have mostly won over SVN and Hg, it doesn't follow that it's because of its UI. (For example, I think that a lot of Git's success actually comes from the UI of GitHub, not Git itself, but I don't have... - Source: Hacker News / almost 4 years ago
Do you know an article comparing Gitless to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Gitless. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.