Overview
| Comment: | land required-check-names |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
137b3a5e1e14e4241c2623f72a59e214 |
| User & Date: | dmestas on 2026-09-13 20:47:59.318 |
| Other Links: | manifest | tags |
Context
|
2026-09-13
| ||
| 21:14 | checks: the panel and the accept ask one question with one rule closed check-in: 58989b59ea user: dmestas tags: check-name-one-rule | |
| 21:09 | land forge-bucket check-in: 729e581fc8 user: dmestas tags: trunk | |
| 21:08 | a forge may supply the storage, so bringing your own is a choice closed check-in: 81cae7060a user: dmestas tags: forge-bucket | |
| 21:06 | landings: every accept state has a control, asserted on a hook not a word closed check-in: 0b58e6f3d6 user: dmestas tags: accept-state-guard | |
| 20:47 | land required-check-names check-in: 137b3a5e1e user: dmestas tags: trunk | |
| 20:47 | land autoland-why check-in: 7a1d5873ff user: dmestas tags: trunk | |
| 20:36 | a required check matches the pipeline's name, not the engine's closed check-in: 574315ba71 user: dmestas tags: required-check-names | |
Changes
Modified internal/api/register.go
from [2929d0f0de]
to [2e84c75f27].
[diff]
Added internal/api/requiredchecks_test.go version [bb9b524af6].