# What Gitsu does and does not do versus github.com

> **TL;DR** Gitsu audited every operation github.com offers on a project, an issue and everything attached to them, then checked each against its own code. The tables below show, per capability, which operations Gitsu does, does partly or does not do yet, with the overall counts.

This page lists what Gitsu can and cannot do next to github.com, one operation at a time. The tables below are built from Gitsu's parity audit when the site is built, so the counts on this page are the audit's counts. Most gaps are real, and many are large: github.com does much more than Gitsu does today.

## What does the audit measure?

It measures, for every operation github.com offers on a project, an issue, or anything attached to them, whether a Gitsu user can do the same thing. An operation is a concrete action such as "add an assignee who is not already on the issue" or "set a milestone's due date", not a feature name. Labels, milestones, custom fields, views, sub-issues, comments and the project itself are each broken down into their create, read, update and delete actions.

Each operation gets one of three answers:

- **Done**: Gitsu does it, with a matching control a user can reach.
- **Partial**: Gitsu does some of it, such as fewer options than github.com, only some of the places github.com offers it, or a path that only works in some cases.
- **Missing**: Gitsu does not do it yet.

The note beside each row is the audit's one-line description of the gap, or where the control lives in Gitsu when it is done.

## How was it run?

It was run on 5 August 2026, in three steps, against a demo repository and project on github.com.

First, the audit established what github.com offers from three sources: GitHub's GraphQL schema, which lists 258 mutations; a signed-in pass over github.com's own menus, settings pages and pickers; and Gitsu's product requirements, which record what Gitsu leaves out on purpose.

Second, an auditor per capability area checked each operation against Gitsu's source code. Every answer carries evidence: a file and line in Gitsu for a done row, or the search that proved a control is absent for a missing one.

Third, a verifier went over every area and tried to refute each claim. That pass overturned 70 claims, added 103 operations the auditors had missed, and struck 5 rows as false alarms. The verifier's corrections win over the auditor's answers, false alarms are left out of every count, and the rows it added are counted with the rest.

## How should I read the counts?

Read them as a map of where Gitsu is thin, not as a score. The counts include only operations github.com offers, so an action github.com cannot do never counts as a gap. Every operation counts once, whether it is a rarely used setting or the main way people assign work, so a group with many missing rows may still cover the actions you use every day.

The audit has not been re-run since August 2026. Features Gitsu shipped after that date can still show as missing, so check the [getting started guide](/docs/getting-started) and the Web App itself for what is there today.

## Where does github.com win?

On most operations. github.com is the full product, and Gitsu is a faster client for part of it. Project workflows, insights, most project settings, many view options and much of issue administration are only on github.com, and the tables show each one.

Gitsu keeps your data in GitHub, so nothing is lost by using both: do the daily work in Gitsu and open github.com for the rest. The [pricing page](/pricing) explains what the free Web App and a subscription include.

## Frequently asked questions

### Does Gitsu replace github.com?

No. Gitsu works on top of GitHub Issues and GitHub Projects, and github.com still does far more. Anything Gitsu cannot do, you can still do on github.com against the same issue or board.

### When was the audit run?

On 5 August 2026. The tables show Gitsu as it was then; the audit has not been re-run since, so a feature shipped later can still show as missing.

### How is an operation marked partial?

Partial means Gitsu offers the operation but not the whole of it: fewer options than github.com, only some of the places github.com offers it, or a path that works only in some cases.

### Why are some things github.com offers not counted?

Parity is counted only over operations github.com actually offers. Rows the verifier struck as false alarms are left out of every count.