{{define "pipeline_settings"}}{{template "top" .}}
{{if .Flash}}<p class="banner">{{.Flash}}</p>{{end}}
{{if .FlashErr}}<p class="banner error">{{.FlashErr}}</p>{{end}}
{{template "appnav" .}}

<div class="settings-layout">
<nav class="settings-nav" aria-label="Settings sections">
  {{range .SettingsNav}}<a href="{{.Href}}"{{if .Current}} aria-current="page"{{end}}>{{.Label}}</a>{{end}}
</nav>
<div class="settings-content">
<h2>Release pipeline</h2>
<p class="small">The ordered list of channels a release moves through — the first is where
<code>carlos deploy</code> lands. Each channel can ask for a passkey and a number of members
to confirm before a promotion onto it, or an edit to it, lands. One channel needs none of
this at all — the vocabulary only shows up once you add a second.</p>

{{if .PipelineIsDefault}}
<div class="tiles">
  <form method="post" action="{{.Base}}/apps/{{.AppName}}/pipeline" class="inline">
    <input type="hidden" name="csrf" value="{{.CSRF}}">
    <button type="submit" name="action" value="template-edge-production" class="btn-sm">Edge → Production</button>
  </form>
  <form method="post" action="{{.Base}}/apps/{{.AppName}}/pipeline" class="inline">
    <input type="hidden" name="csrf" value="{{.CSRF}}">
    <button type="submit" name="action" value="template-full-ladder" class="btn-sm">Full ladder</button>
  </form>
</div>
<p class="small">Pick a starting point, then save it or edit it further below — or build your own
from scratch with the row below. Nothing is written until you press Save.</p>
{{end}}

<form method="post" action="{{.Base}}/apps/{{.AppName}}/pipeline">
  <input type="hidden" name="csrf" value="{{.CSRF}}">
  {{/* First submit button in tree order, so pressing Enter in a row's text
       field submits Save — implicit form submission uses the first submit
       button, and without this a row's own "Remove" button would be it. */}}
  <button type="submit" name="action" value="save" class="visually-hidden" tabindex="-1" aria-hidden="true"></button>
  <div class="tablewrap">
  <table>
    <tr><th>Channel</th><th>Bake</th><th>Passkey</th><th>Promote approvals</th><th>Change approvals</th><th></th></tr>
    {{range $i, $row := .PipelineRows}}
    <tr>
      <td><input type="text" name="ch.{{$i}}.name" value="{{$row.Name}}" placeholder="channel-name"
        aria-label="Channel {{$i}} name"></td>
      <td><input type="text" name="ch.{{$i}}.bake" value="{{$row.Bake}}" placeholder="24h"
        aria-label="Channel {{$i}} bake window"></td>
      <td><input type="checkbox" name="ch.{{$i}}.passkey" value="1"{{if $row.Passkey}} checked{{end}}
        aria-label="Channel {{$i}} needs a passkey"></td>
      <td><input type="number" min="0" name="ch.{{$i}}.promote_approvals" value="{{$row.PromoteApprovals}}"
        aria-label="Channel {{$i}} promote approvals"></td>
      <td><input type="number" min="0" name="ch.{{$i}}.change_approvals" value="{{$row.ChangeApprovals}}"
        aria-label="Channel {{$i}} change approvals"></td>
      <td><button type="submit" name="action" value="remove-{{$i}}" class="btn-sm btn-danger">Remove</button></td>
    </tr>
    {{end}}
  </table>
  </div>
  <button type="submit" name="action" value="add" class="btn-sm">Add channel</button>
  <button type="submit" name="action" value="save" class="btn">Save</button>
</form>
<p class="small">Promoting into a channel with rules follows the order above; <code>-hotfix</code>
bypasses the order but never the rules. An edit that touches a channel the SAVED pipeline
already guards with change approvals becomes a proposal here too, at the quorum that channel
already demands.</p>
</div>
</div>
{{template "bottom" .}}{{end}}