Write the commit. Choose when it happened.

A small app that does one thing properly.

• Any date, any time

  Down to the minute, not just the day. A week you backfill looks like a week you worked, because the commits land at the hours you would have been working.

• The Git you already have

  Riggit drives the Git on your machine. Your SSH keys, credential helpers, hooks, aliases and remotes all apply, unchanged. If you can push to a repository today, you can use Riggit with it.

• Stage and sync in the same step

  Three toggles beside the commit button, all off by default except staging. Syncing pulls what is new from the remote before committing, then pushes, so a branch that has moved on is not a rejected push and a dead end.

• Identity, settled once

  Riggit reads the name and email your repository already commits under, falls back to your global config, then to your last commit. It asks only when there is genuinely nothing to find.

• Offline is a normal state

  A commit is local. If the push fails because you are on a train, the commit still stands and Riggit tells you exactly that, rather than reporting the whole thing as a failure.

And a longer list of things it will not do.

Riggit writes to your Git history. That is worth being precise about, so here is the boundary, stated as what cannot happen rather than as a promise that everything is fine.

• It never rewrites history

  Riggit only ever creates new commits. It does not amend, rebase, squash or force anything, and a commit that already exists is left exactly as it is.

• It never touches a repository you have not opened

  Nothing happens in the background and nothing is scanned. Riggit works on the repositories you have added, one at a time, when you press the button.

• It never asks for your GitHub password

  Signing in is optional and goes through GitHub's own device flow, so Riggit never sees a password. It reads your profile and email addresses, so your commits carry an address GitHub recognises, and asks for nothing else unless a push is refused and you choose to allow it.

• Your code never leaves your machine

  The only thing that goes anywhere is the syncing you asked for, to the remote you already had, over the connection Git already uses.

What you need.

Git

Any recent version, already installed

macOS

11 Big Sur or later

Windows

10 or later

Linux

A recent distribution with WebKitGTK

Riggit does not bundle its own copy of Git. It uses yours, which is what keeps your existing setup working and is why there is nothing to configure after installing.