Radix tooltip explains why the Create button is disabled
The "Review name" and "Workflow name" inputs in the creation modals are styled as large serif headings, so users miss them and assume the greyed-out Create button is broken. easterbrooka iterated through three commits to fix it, landing on a Radix tooltip as the final approach.
The first commit (12ed264) added a native title attribute to the Create button in AddNewTRModal.tsx - "Review name required" or "Select a project" depending on which condition blocked submission. The second (a1c8bd1) mirrored the same fix into NewWorkflowModal.tsx.
That approach broke immediately in practice: native title tooltips don't fire reliably on disabled <button> elements because disabled elements don't receive mouse events. The third commit (766d170) replaces both with @radix-ui/react-tooltip. The implementation wraps the disabled button in a <span tabIndex={0} className="inline-block"> to capture hover events, then renders a TooltipProvider / TooltipTrigger / TooltipContent stack around it. The disabledReason logic is pre-computed into a variable (null when the button is enabled, a string when it isn't) so the tooltip only renders when there's actually something to say.
The same commit adds amplify.yml to the repo root, switching the Amplify build from npm ci to npm install --legacy-peer-deps. That's a fork-specific deploy decision, not something to bring across - npm ci's lockfile-strict guarantee is worth keeping, and the npm install swap was only there because adding @radix-ui/react-tooltip without regenerating the lockfile would have broken ci.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?