<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>siGit Code & Deploy</title>
    <link>https://getsigit.5mb.app/</link>
    <description>Plumbers, potters, & deployers.</description>
    <language>zh-CN</language>
    <lastBuildDate>Sun, 12 Apr 2026 10:15:38 GMT</lastBuildDate>
    <atom:link href="https://getsigit.5mb.app//rss.xml" rel="self" type="application/rss+xml" />
    
      <item>
        <title><![CDATA[Features]]></title>
        <link>https://getsigit.5mb.app//features/</link>
        <guid>https://getsigit.5mb.app//features/</guid>
        <pubDate>Wed, 15 Jan 2025 00:00:00 GMT</pubDate>
        <content:encoded><![CDATA[## Git operations

siGit covers the Git workflow you use most often. From the app you can:

- Clone repositories over HTTPS or SSH
- Stage files and write commit messages
- Push to and pull from remote branches
- Fetch to see what's changed upstream without merging
- Create, switch, and delete branches
- Merge branches
- View commit history

It handles the day-to-day stuff well. It is not trying to replace every flag and option in the CLI — if you need `git rebase -i` or complex conflict resolution, open your laptop.

## Diff viewer

Before you commit, you can see exactly what changed. Modified lines are highlighted inline, so you can catch a stray debug log or a half-finished change before it ends up in the repo. Viewing diffs on a phone screen takes some scrolling, but the information is all there.

## Code viewer

Browse any file in a cloned repo with syntax highlighting. Useful for reading through code, checking a config value, or verifying what's actually in a file on a given branch. Editing is supported for straightforward changes — fixing a typo, bumping a version number, updating a config.

## SSH key management

Generate or import SSH keys directly in the app. Keys are stored in the device keychain. You can use different keys for different hosts if needed.

HTTPS authentication also works — paste a personal access token and you're set.

## smbCloud deploy

If you use [smbCloud](https://www.smbcloud.xyz/) for hosting, siGit can trigger a deployment in one tap after you push. No browser required, no copying URLs. Just push and deploy from the same screen.

This requires a smbCloud account with a project configured. If you don't use smbCloud, the rest of the app works fine without it.

## Offline access

Once a repo is cloned, you can browse files, read commit history, and view diffs without a connection. You need network access to push, pull, fetch, or clone.

## Platform support

- iOS (iPhone and iPad)
- Android
- Windows

## Dark mode

Both light and dark themes are supported, following your system setting.

---

## Download

- [App Store](https://apps.apple.com/app/id6753018849) — iOS
- [Google Play](https://play.google.com/store/apps/details?id=xyz.smbcloud.SiGit) — Android
- [Microsoft Store](https://www.microsoft.com/store/apps/xp9k321rf5mzsz) — Windows]]></content:encoded>
      </item>
    
      <item>
        <title><![CDATA[Getting started]]></title>
        <link>https://getsigit.5mb.app//getting-started/</link>
        <guid>https://getsigit.5mb.app//getting-started/</guid>
        <pubDate>Wed, 15 Jan 2025 00:00:00 GMT</pubDate>
        <content:encoded><![CDATA[# Getting started with siGit

siGit is a Git client for iOS, Android, and Windows. This guide walks you through the first few things you'll need to do to clone a repo and get to work.

## Download the app

Pick your platform:

- **iOS** — [App Store](https://apps.apple.com/app/id6753018849)
- **Android** — [Google Play](https://play.google.com/store/apps/details?id=xyz.smbcloud.SiGit)
- **Windows** — [Microsoft Store](https://www.microsoft.com/store/apps/xp9k321rf5mzsz)

## Set up authentication

Before you can clone anything, you need to tell siGit how to authenticate with your Git host (GitHub, GitLab, Bitbucket, self-hosted, etc.).

### SSH key

This is the recommended approach. In the app:

1. Go to **Settings → SSH Keys**
2. Tap **Generate new key** — siGit creates an Ed25519 key pair on your device
3. Copy the public key and add it to your Git host (GitHub: *Settings → SSH and GPG keys → New SSH key*)

That's it. The private key stays on your device.

If you already have an SSH key you want to use, you can import it instead.

### HTTPS

If you prefer HTTPS, enter your username and a personal access token (not your account password) when prompted during clone. Most Git hosts have deprecated password auth for HTTPS, so make sure you're using a token.

## Clone a repository

1. Tap the **+** button on the home screen
2. Choose **Clone**
3. Paste the repository URL — SSH or HTTPS both work
4. Pick a local name and location if you want to change the defaults
5. Tap **Clone**

Cloning happens in the background. For large repos on a slow connection this can take a moment.

## Browse files and commits

Once cloned, you'll land on the repository view. From here you can:

- Tap any file to open it in the built-in code viewer, which has syntax highlighting for most common languages
- Switch to the **Commits** tab to browse history — tap a commit to see the diff for that change
- Switch branches from the branch selector at the top of the screen

You can browse files and history without a connection if you've already cloned the repo locally.

## Make a commit

1. Edit a file in the code editor, or make changes through another tool that has access to the same local repo
2. Go to the **Changes** tab — you'll see all modified and untracked files listed
3. Tap a file to review the diff before staging it
4. Stage the files you want to include, write a commit message, and tap **Commit**

If you're mid-thought on a commit message and want to double-check the diff again, the staged files stay staged until you explicitly unstage them.

## Push to remote

After committing, tap **Push**. If your branch has no upstream yet, siGit will ask you to set one. Pick the remote (usually `origin`) and the branch name, then confirm.

If the push is rejected because the remote has commits you don't have locally, pull first, resolve any conflicts, then push again.

## Pull and fetch

- **Pull** downloads new commits and merges (or rebases) them into your current branch
- **Fetch** downloads remote changes without touching your working copy — useful for checking what's changed before deciding what to do

Both are available from the repository action menu.

## Manage branches

From the branch selector you can:

- Switch to an existing branch
- Create a new branch from your current HEAD
- Delete a local branch

Merging is done from the branch view — select the branch you want to merge into the current one and confirm.

## Deploy with smbCloud

If you have an smbCloud account and your project is connected, a **Deploy** button appears in the repository toolbar. Tap it to trigger a deployment of the current branch. You can watch the deploy status update in real time without leaving the app.

If you're not using smbCloud, you can ignore this entirely — it's opt-in.

## A few things worth knowing

- Dark mode follows your system setting, but you can also pin it in **Settings → Appearance**
- SSH keys are stored in the device's secure enclave where supported
- Files you've already cloned are available offline; pushing, pulling, and cloning require a connection
- The code editor is for reviewing and making small edits — it's not a full IDE]]></content:encoded>
      </item>
    
      <item>
        <title><![CDATA[Why siGit]]></title>
        <link>https://getsigit.5mb.app//why-sigit-code-deploy/</link>
        <guid>https://getsigit.5mb.app//why-sigit-code-deploy/</guid>
        <pubDate>Wed, 15 Jan 2025 00:00:00 GMT</pubDate>
        <content:encoded><![CDATA[# Why siGit

If you never leave your desk, you probably don't need this. That's worth saying upfront.

siGit is a mobile Git client. It exists because developers don't always have a laptop nearby, and sometimes things can't wait until you do.

## The actual use cases

### A hotfix at the wrong time

You're away from your desk — weekend, evening, on a train — and someone reports a bug in production. The fix is one line. You know exactly what it is. Without a mobile Git client, your options are to find a laptop, borrow one, or wait. With siGit, you clone the repo (or switch to an already-cloned one), make the change, commit, push. Done.

That's the main reason this app exists.

### Reviewing work on the commute

Reading a diff on your phone isn't as comfortable as a large monitor. But it's better than not reading it at all. If a pull request is waiting and you have 30 minutes on the subway, you can go through the changed files, see what was modified, and arrive already knowing where you stand.

### Checking what's deployed without opening a laptop

Sometimes you just want to know the state of a branch. What's the last commit on main? Did that deployment go out? You don't need a full IDE for that — you need to see the log. siGit lets you browse commits and file history from your phone.

### Deploying from your phone when you're on call

siGit integrates with smbCloud. If your project is set up there, you can trigger a deploy with one tap from the app. For people who are occasionally on call or manage production systems, this is genuinely useful.

## What it isn't

It's not a replacement for working in a proper terminal or IDE. You're not going to write an entire feature on your phone. Syntax highlighting makes the code viewer readable, but it's still a phone screen.

siGit handles the operational side of Git — cloning, committing, pushing, pulling, branching, merging — and it handles it well. But if you're doing deep development work, you want a keyboard.

## Who it's for

Developers who occasionally need to do Git operations away from a laptop. That might be a few times a week or a few times a month. The frequency doesn't matter much — what matters is whether those gaps are a problem for you.

If you've ever been stuck waiting to get back to a computer to push something that was already done, or to check something you already knew, then you've felt exactly the problem siGit is built around.

---

Available on [iOS](https://apps.apple.com/app/id6753018849), [Android](https://play.google.com/store/apps/details?id=xyz.smbcloud.SiGit), and [Windows](https://www.microsoft.com/store/apps/xp9k321rf5mzsz). Made by Splitfire AB, Sweden.]]></content:encoded>
      </item>
    
  </channel>
</rss>