◉ANTIGRAVITY LABJP
TAG

Git

26 articles
← Back to all tags
Related:
Antigravity12antigravity10workflow6agents4troubleshooting4automation3editor2agent2verification2Antigravity CLI2Agent Operations2CI2
◉ Antigravity/2026-10-15Beginner

Before You Press Delete on an Antigravity Project, Can You Name Three Things That Stay?

Does deleting a project in Antigravity 2.0 remove your source code? A community explanation, split into its two storage locations, plus a read-only script and a safe order for freeing disk space.

⟐ Editor/2026-10-08Beginner

Undo That Rewinds Only the Conversation, and Messaging a Subagent Directly: Three Moments I Hesitated

Antigravity 2.19.1 adds undo for the conversation only, and direct messages to a subagent. Here is what the changelog says, where I draw my own lines, and how to check both safely.

⚙ AI Tools/2026-10-01Beginner

You Don't Need to Read Commands: Three Places to Check When an Agent Works

If strings of terminal text make the approve button feel risky, here is a way to check just three things: a way back before you start, the first word of a command, and the diff afterward.

⟐ Editor/2026-09-03Intermediate

How much of Antigravity's generated commit message I actually keep

Where the Review pane's generated commit message stops being enough, and where I start writing. A prepare-commit-msg hook that adds a Why trailer, plus measured behaviour during rebase, cherry-pick and revert.

⟐ 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.

✦ Tips/2026-04-27Intermediate

Half-Automating CHANGELOG.md From git log With Antigravity — A Solo Developer's Decision Log

You opened your code from six months ago and forgot why you made that change. A common solo-dev problem. Here's a half-automated workflow that uses Antigravity to draft CHANGELOG.md entries straight from your git log, with a working shell script.

◈ 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.