DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to move repository state into SQLite or PostgreSQL and object storage with Git AI

Add a graft storage section, import in shadow mode, then switch to authoritative.

Who it is forA platform engineer who needs to run several gitai server nodes that scale out and share one consistent state.

The problemLocal Git repositories on one machine cannot be shared safely by several server nodes handling many agents.

The outcomeRepository state is kept in a database with a changeset log and packs live in object storage, and any server node can rebuild its cache.

What you need first

  • Linux or macOS
  • Go 1.26
  • A C toolchain
  • Meson and Ninja (the build compiles a bundled Git)
  • Git and a clone of https://github.com/feder-cr/git-ai.git

Steps

  1. Read doc/graft/STORAGE.md for the storage core design and the supported database and object storage options.
  2. Copy examples/graft/config.toml and adapt it for your server.
  3. Add a [graft.storage] section and start in shadow mode.
  4. Import your repositories while the server runs in shadow mode.
  5. Switch the storage mode to authoritative as described in doc/graft/STORAGE.md.

Prompt for your agent

In the repository git-ai, read doc/graft/STORAGE.md and list the storage modes and the supported database and object storage backends. Start the server with `_build/bin/gitaly serve config.toml` using your storage section, and confirm the server runs in shadow mode before any switch.

Caveat. The README lists garbage collection of packs in the storage core as a known gap, so storage will grow until that is handled.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page