Code review that doesn’t leave the ticket.
Most tools treat a pull request as its own separate object, linked back to an issue. GForge doesn’t — the ticket you’re already working in is where the review happens, from first comment to final merge.
The ticket is the review — not a link to one
Comment on any line of a diff, right inside the ticket. Mention a teammate and they’re notified. And because comments are tied to the commit, not the branch, that history survives long after the branch is deleted.
A real inline comment, posted directly on the diff.
Screenshot pending — ticket timeline view
(tracked in #65636)
That same comment, on the ticket’s own activity timeline.
Know if it merges — and know where it’s actually deployed
Conflict detection and deployment status, both visible before you touch a terminal.
Before you even click merge, GForge runs a real three-way merge check and tells you immediately if there’s a conflict — not a guess, an actual dry run against your target branch.
Set up a Promotion Model once — the ordered sequence of branches your code moves through, like gforge-next → gforge-next-deploy → gforge-com → master. Every ticket then shows exactly where its code stands: green means it’s live in that branch, red means it isn’t there yet, and yellow means it was there before but got sent back for rework and has to work its way through again. No more asking a developer “has this shipped” or “can I test this in QA” — just look at the ticket.
The fundamentals, done right
Git and SVN, Your Choice
Host either, or both, wherever you need them — cloud, self-hosted, or fully air-gapped.
Your Branch, Automatically Linked
Name a branch some-bug-to-fix-#1234, and because the ticket number is right there in the branch name, every commit you push to it links back to ticket #1234 automatically — no need to reference the ticket in each individual commit message (though you still can, if you want to). GForge’s own engineering team runs on exactly this pattern, tracking each ticket’s Work Branch directly on the ticket.
Built for Big Files Too
Git LFS is supported out of the box, so large binary assets don’t bloat your repository.
Browse Any Branch
Dig into any branch’s file tree directly in the browser — no local checkout required.
Full Commit History
Pick a branch and see every commit in reverse chronological order, complete with author and message.
Merge Without a Ticket, When You Need To
Prefer to skip the ticket workflow for a quick prototype? You can still merge one branch into another right from GForge’s web UI — no ticket required, the same arbitrary merge you’d otherwise do from the command line.
Real access control, not just permissions
Every branch, every role, every commit — configurable, and enforceable, not just suggested.
Commit governance, configured once per repository.
Per-branch, per-role access — down to who can even write to production.
- Require every commit or branch name to reference a real ticket — not optional, enforced server-side
- Enforce the Conventional Commits v1.0.0 spec, if your team wants standardized commit messages
- Validate that commits match the authenticated committer’s email, and that assigned tickets match the person committing
- Lock any branch to read-only for specific roles — an intern can read
master, only senior developers and CI can write to it
See your own repos, reviewed this way.
Start free, or talk to an engineer about migrating your existing history over.