cachenoob.blogg.se - Git gui client with multiple users

Git gui client with multiple users how to#
Git gui client with multiple users manual#
Git gui client with multiple users software#
Git gui client with multiple users free#

GitQlient can be executed from command line with additional params.

This view is visible and accessible when GitQlient detects that there is a conflict caused by a merge, cherry-pick, or pull action. There is another view but is not accessible always: it is the Merge View. These views, when enabled, can be accessed by the Controls placed at the top of the repository window.

The Tree View (or Main Repository View).

Since the beginning I divided GitQlient three big sections depending on their functionality: Unfortunately there are no cross-repository features. All the features of GitQlient will be presented along the User Manual: all of them apply to all the opened repositories individually. All repositories are managed in the same isolated way. Usually refers to the local modification in files of the repository that are not committed yet.Īs I explained in the introduction, GitQlient support multiple repositories opened at the same time. Here you can find all the specific glossary that will be used in this document referring to GitQlient: This document tries to cover exactly that.

Git gui client with multiple users how to#

What options they have and how to deal with possible mistakes or errors.

Git gui client with multiple users manual#

When I write the code of a project or a feature, I don’t need to write a User Manual to know how it works I’ve created it!īut, what happens if you want to introduce as much people as possible? Well, then we need a User Manual that tells them exactly how things work.

Git gui client with multiple users software#

After several years in the software industry, I’m aware that one thing is writing the code of an application and another completely different is to be able to explain how to use it.

The second thing I’ve been missing is a proper User Manual. I’d like that this technical documentation helps whoever wants to contribute to the project. I mean also to provide documentation about how the application is designed and why I did it in that way. I’m not talking only about adding Doxygen documentation to the header files or the APIs.

There are several things, but I feel that two in particular are missed most of the time. Some of them are application-based but other’s are related with the spirit of the open source. This was one feature, but there are several other. That’s why I decided to include the feature of multiple repositories in the same view as part of GitQlient since version 1.0.0. Among the features I was missing, one in particular was really painful: most of the apps only allow one repository opened at the same time.

Git gui client with multiple users free#

On that version, some features that were not part of QGit were included to make it easier to handle the Git repository.Īfter that, I felt free to open the gates for the big new features that I was actually missing in some of the Git clients I was using. That was achieved in the version 1.0.0 of GitQlientPlugin in December. The primarily idea behind GitQlient was to modernize the old code that QGit is based on and provide a easy UI/UX that I was actually missing on other clients. This idea has grown since the day 1 to not only cover the integration with QtCreator but also to make it an app on it’s own. The original idea was to provide a GUI-oriented Git client that was easy to integrate with QtCreator (currently shipped as GitQlientPlugin). Nowadays it goes beyond of just a fork and adds a lot of new functionality. GitQlient, pronounced as git+client (/gɪtˈklaɪənt/) is a multi-platform Git client originally forked from QGit. GitQlient is maintained by francescmm GitQlient User Manual Introduction Nowadays it just keeps some old functionality to store the data that is used to later paint the repo tree.