Changelog

Global search finds more of what you type

2026-10-02

The search in the top bar got a round of matching fixes:

• Repos, reviews, and files match your words in any order, and dashes, slashes, and underscores no longer get in the way.
• Files also match when the letters of your query appear in order, ranked after closer matches.
• A query naming a repo puts that repo first.
• path/to/file.go:42 opens the file at line 42.
• app R12 (or alice/app R12, or app#R12) jumps to review R12 in that repo.
• Opening an empty search box lists the repos and reviews you opened recently in this browser.

Retargeted stacks sync cleanly

2026-10-02 · gs 0.7.1

A stack built on main and then retargeted to a release branch still holds main's commits locally. gs 0.7.0 counted those commits as work that only existed on your machine, so gs sync refused to adopt the server's rebase, and gs cleanup and the branch reset after a land refused too.

gs 0.7.1 knows commits that are already on main or on the stack's base are safe on the server, and judges only the stack's own commits.

brew upgrade alethi-dev/tap/gs

Stacks can land into any branch

2026-10-01 · gs 0.7.0

A stack used to land into the repo's default branch, always. Now each stack has its own base, so you can carry a fix on release/1.x the same way you work on main.

Name the base on the stack's first review. Later reviews inherit it, gs submit lands into it, gs sync restacks onto it, and gs stack prints lands into release/1.x.

gs worktree add hotfix --base origin/release/1.x
gs review create --base release/1.x -t "fix: release crash"

To move a stack you already have, retarget it on the server, then adopt the result locally:

gs review rebase --stack --onto release/1.x
gs sync

On the web, the new-review popover on a repo's home page has an "into" picker that records the base the same way.

Every machine that touches a stack with a base needs gs 0.7.0 or newer. An older gs stops with unknown field "base"; upgrade with brew upgrade alethi-dev/tap/gs.

Landing policy in repo settings

2026-09-27

Repo settings now has a Landing policy section. It shows what every land needs and lets you edit it:

• how many LGTMs a review needs,
• whether requested reviewers must approve,
• whether repo owners can land without approval,
• which checks must pass.

Policy lives in .gitstack/policy.toml, so the form doesn't change it directly. Saving proposes the change as a review on the settings/policy branch, and it takes effect when a repo owner approves and lands that review. Policy changes get reviewed like code.

Org members page

2026-09-27

Each org has a members page at /<org>/-/members. It lists every member with their role and join date, and you can search, sort, and switch between All, Owners, Admins, and Members.

The org home also shows the first 10 members, with a link to the full list. Both are visible to the org's members and to site admins.

Every stack in a repo on one page

2026-09-26

The Open stacks list on a repo's home page stops at 10. Every stack now has a home on the Stacks page at /<namespace>/<repo>/stacks.

It has tabs for open, landed, and abandoned stacks, and filters for open ones: Mine, Needs my review, Ready to land, Blocked, and Stale (no push in 7 days). You can search, sort by last update, creation, or size, and page through the results. Each row shows the stack's status, reviews, approvals, and open threads, and the list refreshes as people push.

A new top bar with global search

2026-09-25

Every page now has the same 48px top bar:

• Search (Cmd K, or Ctrl K off a Mac) finds repos, reviews, and files. Typing a page name like settings, billing, or stacks jumps straight there.
• Switchers next to the logo move between your namespaces and their repos.
• Queue shows what is waiting on you, grouped by why.
• The help and account menus hold docs, feedback, theme, and settings.