Omnigit 0.5.0

Create a new repository from inside Omnigit, and publish it to GitHub, Gitea or GitLab in the same step, with a README, a .gitignore and a licence of your choosing. Omnigit now also reopens whichever repository you had open last.

Install

Linux — .deb (Debian/Ubuntu/Mint), .rpm (Fedora/RHEL/openSUSE), .flatpak (flatpak install ./Omnigit-0.5.0-x86_64.flatpak), the .AppImage (anywhere else — chmod +x it and run it, no install), or the portable .tar.gz.
Windows — run the -setup.exe, or unzip the portable build.
macOS — open the .dmg and drag Omnigit to Applications.

The macOS builds are signed and notarised — the .dmg opens and Omnigit launches with nothing to click past. The Windows builds are unsigned, so the first launch needs one nudge: click More info → Run anyway, and for the portable .zip you may also need right-click the .exe → Properties → Unblock.

No git installation is required. The native libgit2 library ships inside the app, along with everything else it needs.

Verify a download against SHA256SUMS: sha256sum -c --ignore-missing SHA256SUMS.

Getting started

Add a clone you already have from the + in the header, or sign in under Settings → Accounts and clone one straight from that menu's Clone from a hosting site… entry. GitHub supports browser sign-in; anywhere else takes a personal access token. Tokens go to your OS keychain, never to a settings file.

Omnigit 0.4.7

A clone no longer fills the activity log with thousands of identical lines at 100%; the indexing that follows a download is reported on its own instead, so a large clone says what it is doing rather than appearing to hang.

Install

Linux — .deb (Debian/Ubuntu/Mint), .rpm (Fedora/RHEL/openSUSE), .flatpak (flatpak install ./Omnigit-0.4.7-x86_64.flatpak), the .AppImage (anywhere else — chmod +x it and run it, no install), or the portable .tar.gz.
Windows — run the -setup.exe, or unzip the portable build.
macOS — open the .dmg and drag Omnigit to Applications.

The macOS builds are signed and notarised — the .dmg opens and Omnigit launches with nothing to click past. The Windows builds are unsigned, so the first launch needs one nudge: click More info → Run anyway, and for the portable .zip you may also need right-click the .exe → Properties → Unblock.

No git installation is required. The native libgit2 library ships inside the app, along with everything else it needs.

Verify a download against SHA256SUMS: sha256sum -c --ignore-missing SHA256SUMS.

Getting started

Add a clone you already have from the + in the header, or sign in under Settings → Accounts and clone one straight from that menu's Clone from a hosting site… entry. GitHub supports browser sign-in; anywhere else takes a personal access token. Tokens go to your OS keychain, never to a settings file.

Omnigit 0.4.6

Windows can clone and push again from servers that offer TLS 1.3: git's HTTPS now goes through .NET rather than libgit2, whose Windows TLS cannot survive a session ticket. Failures that were not about sign-in no longer claim the saved token has expired.

Install

Linux — .deb (Debian/Ubuntu/Mint), .rpm (Fedora/RHEL/openSUSE), .flatpak (flatpak install ./Omnigit-0.4.6-x86_64.flatpak), the .AppImage (anywhere else — chmod +x it and run it, no install), or the portable .tar.gz.
Windows — run the -setup.exe, or unzip the portable build.
macOS — open the .dmg and drag Omnigit to Applications.

The macOS builds are signed and notarised — the .dmg opens and Omnigit launches with nothing to click past. The Windows builds are unsigned, so the first launch needs one nudge: click More info → Run anyway, and for the portable .zip you may also need right-click the .exe → Properties → Unblock.

No git installation is required. The native libgit2 library ships inside the app, along with everything else it needs.

Verify a download against SHA256SUMS: sha256sum -c --ignore-missing SHA256SUMS.

Getting started

Add a clone you already have from the + in the header, or sign in under Settings → Accounts and clone one straight from that menu's Clone from a hosting site… entry. GitHub supports browser sign-in; anywhere else takes a personal access token. Tokens go to your OS keychain, never to a settings file.

Omnigit 0.4.5

Fixed a clone or fetch that failed part-way through being reported as a rejected sign-in token, hiding the real reason; Windows paths longer than the system allows are now named as the cause when they are. The activity console can be selected and copied, and a Copy button on it takes the whole log.

Install

Linux — .deb (Debian/Ubuntu/Mint), .rpm (Fedora/RHEL/openSUSE), .flatpak (flatpak install ./Omnigit-0.4.5-x86_64.flatpak), the .AppImage (anywhere else — chmod +x it and run it, no install), or the portable .tar.gz.
Windows — run the -setup.exe, or unzip the portable build.
macOS — open the .dmg and drag Omnigit to Applications.

The macOS builds are signed and notarised — the .dmg opens and Omnigit launches with nothing to click past. The Windows builds are unsigned, so the first launch needs one nudge: click More info → Run anyway, and for the portable .zip you may also need right-click the .exe → Properties → Unblock.

No git installation is required. The native libgit2 library ships inside the app, along with everything else it needs.

Verify a download against SHA256SUMS: sha256sum -c --ignore-missing SHA256SUMS.

Getting started

Add a clone you already have from the + in the header, or sign in under Settings → Accounts and clone one straight from that menu's Clone from a hosting site… entry. GitHub supports browser sign-in; anywhere else takes a personal access token. Tokens go to your OS keychain, never to a settings file.

Omnigit 0.4.3

Branches checked out in another worktree now open that worktree instead of failing halfway through a checkout. The sidebar tells two copies of one project apart, the repository picker moved up into the header, and Omnigit has a new icon.

Install

Linux — .deb (Debian/Ubuntu/Mint), .rpm (Fedora/RHEL/openSUSE), .flatpak (flatpak install ./Omnigit-0.4.3-x86_64.flatpak), the .AppImage (anywhere else — chmod +x it and run it, no install), or the portable .tar.gz.
Windows — run the -setup.exe, or unzip the portable build.
macOS — open the .dmg and drag Omnigit to Applications.

The macOS builds are signed and notarised — the .dmg opens and Omnigit launches with nothing to click past. The Windows builds are unsigned, so the first launch needs one nudge: click More info → Run anyway, and for the portable .zip you may also need right-click the .exe → Properties → Unblock.

No git installation is required. The native libgit2 library ships inside the app, along with everything else it needs.

Verify a download against SHA256SUMS: sha256sum -c --ignore-missing SHA256SUMS.

Getting started

Add a clone you already have from the + in the header, or sign in under Settings → Accounts and clone one straight from that menu's Clone from a hosting site… entry. GitHub supports browser sign-in; anywhere else takes a personal access token. Tokens go to your OS keychain, never to a settings file.

Omnigit 0.4.2

Omnigit now notices a new release while it is running, rather than only on the next launch, and checks again whenever you come back to the window. While an update installs it says so - and where a password is needed it says to look for the prompt, which can open behind the window or on another screen.

Install

Linux — .deb (Debian/Ubuntu/Mint), .rpm (Fedora/RHEL/openSUSE), .flatpak (flatpak install ./Omnigit-0.4.2-x86_64.flatpak), the .AppImage (anywhere else — chmod +x it and run it, no install), or the portable .tar.gz.
Windows — run the -setup.exe, or unzip the portable build.
macOS — open the .dmg and drag Omnigit to Applications.

The macOS builds are signed and notarised — the .dmg opens and Omnigit launches with nothing to click past. The Windows builds are unsigned, so the first launch needs one nudge: click More info → Run anyway, and for the portable .zip you may also need right-click the .exe → Properties → Unblock.

No git installation is required. The native libgit2 library ships inside the app, along with everything else it needs.

Verify a download against SHA256SUMS: sha256sum -c --ignore-missing SHA256SUMS.

Getting started

Add a clone you already have from the + in the header, or sign in under Settings → Accounts and clone one straight from that menu's Clone from a hosting site… entry. GitHub supports browser sign-in; anywhere else takes a personal access token. Tokens go to your OS keychain, never to a settings file.

Omnigit 0.4.1

Repositories can now be removed. Right-click one in the sidebar to take it out of Omnigit, or to move the whole folder to the trash - the second asks first, and tells you what is in there that the remote has not got.

Install

Linux — .deb (Debian/Ubuntu/Mint), .rpm (Fedora/RHEL/openSUSE), .flatpak (flatpak install ./Omnigit-0.4.1-x86_64.flatpak), the .AppImage (anywhere else — chmod +x it and run it, no install), or the portable .tar.gz.
Windows — run the -setup.exe, or unzip the portable build.
macOS — open the .dmg and drag Omnigit to Applications.

The macOS builds are signed and notarised — the .dmg opens and Omnigit launches with nothing to click past. The Windows builds are unsigned, so the first launch needs one nudge: click More info → Run anyway, and for the portable .zip you may also need right-click the .exe → Properties → Unblock.

No git installation is required. The native libgit2 library ships inside the app, along with everything else it needs.

Verify a download against SHA256SUMS: sha256sum -c --ignore-missing SHA256SUMS.

Getting started

Add a clone you already have from the + in the header, or sign in under Settings → Accounts and clone one straight from that menu's Clone from a hosting site… entry. GitHub supports browser sign-in; anywhere else takes a personal access token. Tokens go to your OS keychain, never to a settings file.

Omnigit 0.4.0

Omnigit now updates itself. Settings gained an About tab showing the version you are running and what changed in the newest release, with one button that downloads it, checks it against a published checksum and restarts into it. Every package format does this except the Flatpak, which its sandbox rules out.

Install

Linux — .deb (Debian/Ubuntu/Mint), .rpm (Fedora/RHEL/openSUSE), .flatpak (flatpak install ./Omnigit-0.4.0-x86_64.flatpak), the .AppImage (anywhere else — chmod +x it and run it, no install), or the portable .tar.gz.
Windows — run the -setup.exe, or unzip the portable build.
macOS — open the .dmg and drag Omnigit to Applications.

The macOS builds are signed and notarised — the .dmg opens and Omnigit launches with nothing to click past. The Windows builds are unsigned, so the first launch needs one nudge: click More info → Run anyway, and for the portable .zip you may also need right-click the .exe → Properties → Unblock.

No git installation is required. The native libgit2 library ships inside the app, along with everything else it needs.

Verify a download against SHA256SUMS: sha256sum -c --ignore-missing SHA256SUMS.

Getting started

Add a clone you already have from the + in the header, or sign in under Settings → Accounts and clone one straight from that menu's Clone from a hosting site… entry. GitHub supports browser sign-in; anywhere else takes a personal access token. Tokens go to your OS keychain, never to a settings file.

Omnigit 0.3.0

Automated build of Omnigit 0.3.0.

Install

Linux — .deb (Debian/Ubuntu/Mint), .rpm (Fedora/RHEL/openSUSE), .flatpak (flatpak install ./Omnigit-0.3.0-x86_64.flatpak), the .AppImage (anywhere else — chmod +x it and run it, no install), or the portable .tar.gz.
Windows — run the -setup.exe, or unzip the portable build.
macOS — open the .dmg and drag Omnigit to Applications.

The macOS builds are signed and notarised — the .dmg opens and Omnigit launches with nothing to click past. The Windows builds are unsigned, so the first launch needs one nudge: click More info → Run anyway, and for the portable .zip you may also need right-click the .exe → Properties → Unblock.

No git installation is required. The native libgit2 library ships inside the app, along with everything else it needs.

Getting started

Add a clone you already have from the + in the header, or sign in under Settings → Accounts and clone one straight from that menu's Clone from a hosting site… entry. GitHub supports browser sign-in; anywhere else takes a personal access token. Tokens go to your OS keychain, never to a settings file.

Beyond the usual staging, committing, branching and fetch/push/pull: switching branches with uncommitted work asks whether to bring it along or stash it, the app notices changes made outside it, and hosting sites other than GitHub, Gitea and GitLab can be added under Settings → Hosting sites without writing any code — or by hand, see docs/host-manifests.md.

Not in this build

Pull requests and issues.

Omnigit 0.2.2

Automated build of Omnigit 0.2.2.

Install

Linux — .deb (Debian/Ubuntu/Mint), .rpm (Fedora/RHEL/openSUSE), .flatpak (flatpak install ./Omnigit-0.2.2-x86_64.flatpak), the .AppImage (anywhere else — chmod +x it and run it, no install), or the portable .tar.gz.
Windows — run the -setup.exe, or unzip the portable build.
macOS — open the .dmg and drag Omnigit to Applications.

The macOS builds are signed and notarised — the .dmg opens and Omnigit launches with nothing to click past. The Windows builds are unsigned, so the first launch needs one nudge: click More info → Run anyway, and for the portable .zip you may also need right-click the .exe → Properties → Unblock.

No git installation is required. The native libgit2 library ships inside the app, along with everything else it needs.

Getting started

Add a clone you already have from the + in the header, or sign in under Settings → Accounts and clone one straight from that menu's Clone from a hosting site… entry. GitHub supports browser sign-in; anywhere else takes a personal access token. Tokens go to your OS keychain, never to a settings file.

Beyond the usual staging, committing, branching and fetch/push/pull: switching branches with uncommitted work asks whether to bring it along or stash it, the app notices changes made outside it, and hosting sites other than GitHub, Gitea and GitLab can be added under Settings → Hosting sites without writing any code — or by hand, see docs/host-manifests.md.

Not in this build

Pull requests and issues.