ANTIGRAVITY LABJP
TAG

Git

22 articles
Back to all tags
Related:
Antigravity10antigravity8workflow5troubleshooting4automation3agents3verification2Antigravity CLI2Agent Operations2CI2Agents2quality-gate2
Editor/2026-08-27Intermediate

Building a Verification Loop With Antigravity 2.10.0's Embedded Terminal

Antigravity 2.10.0 puts a terminal in the sidebar. Here is how I pinned my pre-merge checks down to three commands, scoped them to changed files only, and what the measured difference turned out to be.

Tips/2026-08-06Advanced

Seven Characters Don't Only Point at Commits — Measuring When Your Agent's Recorded Hashes Stop Resolving

Short commit hashes recorded by an agent quietly stop resolving as a repository grows. Measuring where ambiguity begins, fixing the recording side, and building a batch verification gate.

Agents/2026-08-05Advanced

Reading the Same History in 38 Seconds — or 0.4: Handing a Read-Only .git to Your Agent

Antigravity CLI 1.1.10 lets the sandbox read .git without write access. I built a per-session history summary two ways, measured a roughly 100x speed gap, traced it to process spawn cost, and added a guard for shallow clones that silently corrupt the numbers.

Agents/2026-07-15Intermediate

When Your Agent Commits a .bak File: Why Fix-Tool Artifacts End Up in Git

Backup files like .bak and .orig slip into commits after an agent runs a --fix tool. Here are the reproduction conditions, the real root cause, and three fixes: narrowing the staged scope, wrapping the fixer, and adding a pre-commit extension gate.

Agents/2026-07-10Advanced

Tracing Why an Agent Wrote That Line Six Months Ago — Commit Granularity and Provenance Trailers

When an agent packs 14 files and 800 lines into a single commit, git blame tells you nothing six months later. Here is how I split commits at intent boundaries, recorded provenance as machine-readable Git trailers, and built a one-command path from a blamed line back to the design decision behind it.

Agents/2026-07-10Advanced

When Your Agent's Files Vanish Into .gitignore — A Pre-Commit Detection Gate

When an agent writes files that match .gitignore, the diff review looks perfect but nothing lands in the commit. Here is a gate script that catches ignored build output before you push, plus the tuning it needs.

Agents/2026-07-08Advanced

Measuring the Rework Rate of What You Delegate to Agents: Drawing Delegation Boundaries with Numbers, Not Instinct

How much should you hand to an agent? I drew that line by instinct for a long time. Here is a practical way to compute a per-category rework rate from your git history and redraw the delegation boundary with numbers, with working code.

Tips/2026-07-05Intermediate

When Your Agent's Commits Pick Up Junk Files: Fixing It With Staging Scope and a Message Convention

Agents tend to run git add -A, sweeping .bak files and caches into your history, and leave a one-word message. Here is how a staging allowlist, a preflight, and a fill-in message template stop it.

Antigravity/2026-07-02Advanced

Parallel Agents Multiply Artifacts Too — Designing Lifespans and Cleanup for Intermediate Outputs

Worktrees, screenshots, temp branches — parallel agents leave debris at parallel speed. A design for defining artifact lifespans and automating cleanup without ever destroying uncommitted work.

Editor/2026-06-26Advanced

Splitting a Giant Antigravity Diff Into Meaningful Commits

Are you committing the agent's 400-line diffs as a single blob? Here is a practical workflow, with scripts, for re-splitting an unreviewable bulk commit into one concern per commit.

Integrations/2026-06-18Intermediate

Gating Your Agent's Commits With pre-commit — Keeping Broken Changes Out of the Main Repo

How to wire up a pre-commit gate that lints, type-checks, runs fast tests, and scans for secrets the moment Antigravity's agent commits — with measured timings and the ordering that keeps it fast.

Antigravity/2026-06-16Intermediate

Putting a Verification Step After 'Done': Confirming What Your Antigravity Background Agents Actually Produced

An Antigravity 2.0 background agent reported 'Done,' yet the output was nowhere to be found. Running several sites on autopilot as a solo developer, I hit this gap more than once. Here is how I learned to check ground truth instead of the agent's self-report.