I’m happy to announce the release of GitQlient 1.3.0
Six months after the last big release, I present a new GitQlient 1.3.0 version. This comes with a lot of new stuff that I’m going to talk about in this post.
In this release I’ve continued UX refactor I started in the previous one. This time I harmonized the styles for both the bright and the dark color schemas. Another part I’ve focused in a follow-up of the last release, one of the main focus areas has been the UX in the commit area and in the code editor (adding search).
The second big area has been extending the support of GitQlient for other platforms as Haiku, providing RPMs for CentOS and Fedora and removing submodules to facilitate the release in ArchLinux.
The last area but the most important one is about the new functionality and the improvements that GitQlient 1.3.0 includes. This will need a new section, of course. One of the big changes is the inclusion of new Qt dependencies: WebEngineWidgets and WebChannel.
GitQlient 1.3.0 binaries
You can find the binaries for GitQlient 1.3.0 on the release section on the GitHub repo:
New features in GitQlient 1.3.0?
- GitHub integration
- Jenkins integration (preview)
- Stage chunk
- Deleting submodules
- Edit Git/GitQlient configuration in place
- Translations enabled
One of the new things in this GitQlient 1.3.0 is the extension of the GitHub integration and the addition of Jenkins integration (as preview).
With the GitHub integration it is possible now to create issues and PRs. You can do code reviews of a PR with code extracts, comments, reviews and markdown support as well.
The other big feature, Jenkins, it’s in an early stage. You will be able to review the status of your remote Jenkins server, trigger builds and check the result of the different builds.
Finally, not a big feature but a nice to have one is the Pomodoro. GitQlient is becoming more a workspace manager than a simple GitQlient. So, I thought that having a pomodoro clock in GitQlient would be a nice to have feature.
The UX/UI refactor I’ve been doing would be included in the minor features. Unfortunately, it doesn’t bring any really big change, but I hope it simplifies workflows when doing certain Git operations. Among other changes I’ve included:
- Showing if commits are signed: The History view now shows a green check on the author column if the commit is signed
- Search functionality in code editor
- Search functionality for the branches
- Unified untracked and unstaged lists
For the next release there are some nice features I’ve already planned:
- Code refactor: Caused by the big growth of GitQlient.
- Moving commits from UI
- Squashing commits
- DEB packages
- Refactor the GitHub API classes
- Finish Jenkins integration
As a result of the code growth during the last two releases I’d like to improve the structure and readability of it.
Consequently, I wouldn’t expect too many new additions or changes for next release but a better performance and code split to facilitate fixes and app extension in the future.
You can see the release planning and all the features that every release will contain in the Release Plan. And as always, if you’d like some feature or you’re missing something in GitQlient, check that it’s not yet in the backlog and open an issue on GitHub!