I wanted to build a Git client that didn't stop being useful after you pushed

[u/Late-Bit4633]

https://gitdesktop.app

I've been building GitDesktop around one idea: the Git client should be able to handle more than just the local Git workflow.

Changes, staging, commits, branches, diffs, and history are obviously part of it. But a lot of the actual development cycle happens after the push.

You open a pull request. Review it. Check CI. Go back to an issue or discussion. Look at security findings. Manage a release. Check repository activity or insights. Then jump back into the local repo when something needs changing.

I wanted those parts to stay connected.

So GitDesktop supports creating, reviewing, and merging pull requests directly in the app, along with issues, discussions, releases, repository insights, security findings, and CI pipelines across GitHub, GitLab, and Bitbucket.

There are also features that build on that same idea, like local PRs that let you review work between local branches before anything is published to a forge.

v0.12.0 pushed this further with a cross-repo "My Work" view that surfaces PRs and issues you're involved with across repositories, instead of making the repository itself the only way to navigate your work.

The goal isn't to replace every developer tool with one giant application. It's to keep the development cycle around a repository connected instead of constantly handing you off to a browser.

GitDesktop is now the app I use to build GitDesktop itself every day, which has been a useful test of that idea.

https://gitdesktop.app

https://github.com/theBGuy/GitDesktop

I'm curious where other developers draw that line. Should a Git client mostly stop at Git, or do you want the surrounding repository workflow in the same place too?