mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
feat(panel): worked-example tooltip on the environment ladder
The section label now explains the typical dev/slave -> prod/master two-rung setup inline, when to add middle rungs, and what no ladder means.
This commit is contained in:
@@ -1,6 +1,7 @@
|
||||
"use client";
|
||||
|
||||
import { Button } from "@/components/ui/button";
|
||||
import { HelpTip } from "@/components/ui/help-tip";
|
||||
import { Input } from "@/components/ui/input";
|
||||
import { Label } from "@/components/ui/label";
|
||||
import {
|
||||
@@ -57,7 +58,17 @@ export function EnvironmentLadderEditor({
|
||||
return (
|
||||
<div className="space-y-3">
|
||||
<div className="flex items-center justify-between">
|
||||
<Label>Environment ladder</Label>
|
||||
<HelpTip
|
||||
label={
|
||||
"Maps this project's branches to a promotion flow. Typical two-branch setup: " +
|
||||
"rung 1 name 'dev' branch 'slave' (all PRs land there), rung 2 name 'prod' " +
|
||||
"branch 'master' (releases are cut and tagged there). Add middle rungs (qa, " +
|
||||
"staging) only if those branches really exist. No ladder = the default " +
|
||||
"branch plays both roles."
|
||||
}
|
||||
>
|
||||
<Label>Environment ladder</Label>
|
||||
</HelpTip>
|
||||
<span className="text-xs text-muted-foreground">
|
||||
{items.length} rung{items.length !== 1 ? "s" : ""}
|
||||
</span>
|
||||
|
||||
Reference in New Issue
Block a user