TILLFORGE · CODE SEARCH

Find the exact line, at the exact revision.

GA

Search a repository by literal text — from the terminal or the Code tab. Matches are exact and line-numbered, and a result opens straight to the file. There’s no index to build and no query syntax to learn: you type what’s in the code, you get where it is.

01CLI

Search from the terminal

Point forge search at a repo and a phrase. It reads the repository at a revision you choose and returns each match as a file, a line number, and the line itself.

bash
# Literal search across the repo at its default branch.
tilldev forge search acme-api "createPaymentIntent"

# Pin to any revision — a branch, a tag, or a commit.
tilldev forge search acme-api "TODO(security)" --rev release/1.4

# Results are file + line + the matching line, ready to jump to.
02Dashboard

Search inside the repo

The repo’s Code tab has a search box that runs the same search against the revision you’re viewing. Results list every match with its line; selecting one opens the file at that spot, so search flows directly into reading.

03Literal

Exact by design

Search is literal — your query is matched as fixed text, not as a pattern. That means a query like a.b[c] finds exactly that string instead of being read as a regular expression, and there’s no way to craft a query that makes the search expensive. What you type is what’s matched.

Scoped to a revision
Every search runs at one revision — the default branch, or whatever you pass to --rev. Searching a release tag shows exactly what shipped, not what’s on main today.

Next: Repositories to browse the tree, history, and blame that search drops you into. Back to the TillForge overview.