▲ 9 r/git+1 crossposts

GitComet 0.2.0 two months of work squeezed into this release

We just released GitComet 0.2.0 after roughly two months of work on our open-source Git GUI.

A lot of the work wasn't about building huge new features. It was fixing dozens of small workflows and interaction details based on feedback from GitHub, Reddit, and other channels.

During the 0.1.x releases, our main goal was feature parity with existing Git GUI tools. With 0.2.x, we're starting to move beyond that: refining the UI, making it feel more modern, and experimenting with workflows that aren't as common in traditional Git clients.

One example is smaller laptop screens. We wanted the UI to remain useful without everything feeling cramped, so the side panel can now be minimized while keeping its functionality easily accessible.

We also received quite a bit of feedback that the interface didn't feel modern enough. That pushed us to rethink spacing, hierarchy, interactions, and the overall visual style rather than just adding more functionality.

Some of the bigger changes in 0.2.0:

  • New visual design and UI refinements
  • Rebase and interactive rebase support
  • Browse and edit repository files directly inside GitComet
  • Browse files as they existed at a specific point in Git history
  • Worktree changes shown alongside the Git log/history graph
  • Git log filtering by author
  • Improved merge/conflict tooling, including better conflict-marker selection
  • Many more right-click context menus and actions throughout the UI
  • Better responsiveness for smaller screens

Probably the biggest lesson from these two months is that feature implementation is increasingly the easy part. Making dozens of features work together naturally is where a surprising amount of engineering time still goes.

GitComet is written in Rust + GPUI, open source, and free for personal and commercial use.

Website: https://gitcomet.dev/
Repository: https://github.com/Auto-Explore/GitComet

u/Havunenreddit — 4 days ago
▲ 6 r/UI_Design+1 crossposts

Looking for UX Feedback on GItComet UI renewal

Hi everyone,

We're building GitComet, an open-source Git client, and one of the most common pieces of feedback we've received since launch is that the interface doesn't feel modern.

The comments are often quite vague, for example:

>

We're currently renwing the UI and trying to address this feedback. Since our team doesn't include a professional UX designer, we'd really appreciate hearing from people with UX experience.

I attached a video that demonstrates the changes.

  • Repository tabs moved to application title bar similar to web browsers
  • Main content was moved into the darker container
  • Active Repository component is moved behind a toggle next to hamburger menu
  • Back / Forward buttons area feels little empty now?
  • Added more whitespace to many places
  • Sidepanel is now accessible when minimized

Does the new direction feel like an improvement?

  • What stands out to you, either positively or negatively?
  • Does anything still feel dated or inconsistent?

Thanks!

u/Havunenreddit — 22 days ago
▲ 3 r/git

GItComet 0.1.16 - Embedded Terminal, External Code Editor, File directory support

Hey guys! We just released GitComet 0.1.16 and added support for many frequently requested features!

Main highlights:

  • Embedded Terminal - you can now open an embedded terminal within GitComet or configure it to open the external default system terminal
  • File directory support - This is a new view where you can browse all the files available in the working directory, combine this with new functionality where you can browse repository at the point of specific commits, allowing quick traversal of the repository at a specific point of time
  • Integration with external code editor - You can now open files or whole repositories in your favorite code editor.
  • Global back and forward support - This allows you to navigate between user interface changes using back and forward buttons or mouse gestures, similar to web browsers.
  • Command Palette - Allows quick access to all common functionality of GitComet

Next on the horizon is support for rebase, interactive rebase, code review branches, code review commits

Full change log is available at: https://github.com/Auto-Explore/GitComet/releases/tag/v0.1.16

We are also nearing the public launch of GitComet Professional edition you can sign up for the wait list at: https://gitcomet.dev/#editions

u/Havunenreddit — 2 months ago

Anyone here experimenting with autonomous AI for web app testing?

For the past 2 years, we’ve been building a project called AutoExplore.

The basic idea is an agent that interacts with a web application through the UI, keeps exploring it over time, and reports potential issues or unexpected behavior it finds. The goal is not to replace traditional test automation, but to see whether autonomous exploration can help uncover gaps that scripted tests usually miss.

Have you also tried or built something similar?

What I’m trying to understand is where people in QA think this kind of approach is actually useful, and where it breaks down.

We noticed one challenge with this approach is the volume of issues and false positives. We are now trying to tackle that aspect by enriching the observation with source code level information to avoid false positives.

reddit.com
u/Havunenreddit — 3 months ago

Anyone here experimenting with autonomous AI for web app testing?

For the past 2 years, we’ve been building a project called AutoExplore.

The basic idea is an agent that interacts with a web application through the UI, keeps exploring it over time, and reports potential issues or unexpected behavior it finds. The goal is not to replace traditional test automation, but to see whether autonomous exploration can help uncover gaps that scripted tests usually miss.

Have you also tried or built something similar?

What I’m trying to understand is where people in QA think this kind of approach is actually useful, and where it breaks down.

We noticed one challenge with this approach is the volume of issues and false positives. We are now trying to tackle that aspect by enriching the observation with source code level information to avoid false positives.

reddit.com
u/Havunenreddit — 3 months ago

Anyone here experimenting with autonomous AI for web app testing?

For the past 2 years, we’ve been building a project called AutoExplore.

The basic idea is an agent that interacts with a web application through the UI, keeps exploring it over time, and reports potential issues or unexpected behavior it finds. The goal is not to replace traditional test automation, but to see whether autonomous exploration can help uncover gaps that scripted tests usually miss.

Have you also tried or built something similar?

What I’m trying to understand is where people in QA think this kind of approach is actually useful, and where it breaks down.

We noticed one challenge with this approach is the volume of issues and false positives. We are now trying to tackle that aspect by enriching the observation with source code level information to avoid false positives.

reddit.com
u/Havunenreddit — 3 months ago
▲ 12 r/cpp

This week I experienced really interesting bug hunt where Windows ARM target platform started failing CI while other environments passed successfully.

I learnt how to:

  • Use C - programs from Rust programs
  • Compiler configurations are as important as source code
  • What is STATUS_ACCESS_VIOLATION

Hope you like it :)

autoexplore.medium.com
u/Havunenreddit — 4 months ago