easterbrooka makes the grayed-out buttons explain themselves

When you can't click Create, the app now tells you exactly what's missing instead of leaving you to guess.

workflow

Open the dialog to start a new review or a new workflow and the Create button stays grayed out until you've given it what it needs - a name, or a project to file the work under. Until now that button just sat there, inert, with no hint about why. easterbrooka wired in a small hover tooltip that spells it out: name required, or pick a project first. Mouse over the dead button and the reason appears.

It's a minor touch, but a telling one. The explanation only shows up when the button is genuinely blocked, and it's driven by the same check that disables the button in the first place - so the message can't drift out of sync with what the app actually wants. Small polish, done carefully.

So what Anyone rolling this out to non-technical staff will field fewer "why won't it let me click this" questions.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

3 commits from easterbrooka/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`12ed2644`	Add hover tooltip explaining why Create button is disabled	andrew	2026-05-05	↗ GitHub
commit body The Review name field at the top of the New Tabular Review modal is visually subtle (large serif text input that looks like a heading), so users can miss it and assume the disabled Create button is broken. Add a native title attribute that surfaces the gating reason on hover. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
`a1c8bd1e`	Add hover tooltip on disabled Create workflow button	andrew	2026-05-05	↗ GitHub
commit body Same UX problem as the tabular review modal: the Title field is a large serif input that looks ornamental, and users assume the disabled button is broken. Native title attribute surfaces the gating reason on hover. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
`766d170d`	Use Radix tooltip for disabled Create buttons	andrew	2026-05-05	↗ GitHub
commit body Native title-attr tooltips don't reliably fire on disabled <button> elements (browser-dependent). Switch to @radix-ui/react-tooltip with a span wrapper around the disabled button so hover events are captured. - Add @radix-ui/react-tooltip dep - Add components/ui/tooltip.tsx (shadcn-style wrappers) - Wrap the disabled Create button in AddNewTRModal and NewWorkflowModal - Switch Amplify build from npm ci to npm install (committed amplify.yml at repo root) so adding deps doesn't require regenerating the lockfile Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-56.md from inside the repo you want the changes in.

⬇ Download capture-thread-56.md