Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog.d/changed-15712.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
- refactor: split src/docs/labels-and-control-signals.md into per-section pages (#15712)
2 changes: 1 addition & 1 deletion src/docs/adr/0025-central-stage-engine.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ hub read that store and nothing else (`stageStoreOrShared`,
parking stages through the label relay (`agentMayAddLabel`,
`src/pkg/github/issue_request_label.go:75`), so a clanker can set a stage
label and only the next sweep's self-heal corrects it. The docs admit the
arrangement (`src/docs/labels-and-control-signals.md:313-316`). The PR-D
arrangement (`src/docs/labels-and-control-signals/reference.md:313-316`). The PR-D
vocabulary cleanup makes claim labels and review adoption checks use
`stagelabels` directly; their fact-submission migration remains separate.
3. *No explicit transition model.* `Store.Observe` records that a stage
Expand Down
2 changes: 1 addition & 1 deletion src/docs/contributor-relay.md
Original file line number Diff line number Diff line change
Expand Up @@ -1276,7 +1276,7 @@ The prompt forbids printing `no_work_needed` *and* `complete` for one task, but

### fix-pr tasks

The one place a declaration DOES shape dispatch is the stage-072 contributor nudge ([labels-and-control-signals.md](labels-and-control-signals.md#off-the-happy-path-072--nudge--074--takeover)), and only in the client's favour: the hub never grants more than the relay asked for. When one of a contributor's earlier PRs goes red (failing checks, `changes_requested`, conflicts) and the contributor is online — a heartbeat within `governor.labels.stage.presence_window`, default 15m — the hub pushes the diagnosis to their relay as a `task_assign` the relay may receive **while a task is already running**:
The one place a declaration DOES shape dispatch is the stage-072 contributor nudge ([labels-and-control-signals.md](labels-and-control-signals/stage-labels.md#off-the-happy-path-072--nudge--074--takeover)), and only in the client's favour: the hub never grants more than the relay asked for. When one of a contributor's earlier PRs goes red (failing checks, `changes_requested`, conflicts) and the contributor is online — a heartbeat within `governor.labels.stage.presence_window`, default 15m — the hub pushes the diagnosis to their relay as a `task_assign` the relay may receive **while a task is already running**:

```json
{ "type": "task_assign", "task_id": "…", "task_gen": 7,
Expand Down
4 changes: 2 additions & 2 deletions src/docs/dashboard.md

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion src/docs/env-vars.md
Original file line number Diff line number Diff line change
Expand Up @@ -566,7 +566,7 @@ With two or more providers configured, `/login` renders a provider picker; with

| Variable | Required | Default | Purpose |
|---|---|---|---|
| `HIVE_QUESTION_AUTOCLOSE` | No | unset (config `governor.question_autoclose.enabled`, default `false`) | Turns question auto-close on or off, overriding the config value when set to a boolean (`true`/`false`/`1`/`0`). See [labels-and-control-signals.md](labels-and-control-signals.md#question-auto-close) ([#9584](https://github.com/hivecommons/hive/issues/9584)). |
| `HIVE_QUESTION_AUTOCLOSE` | No | unset (config `governor.question_autoclose.enabled`, default `false`) | Turns question auto-close on or off, overriding the config value when set to a boolean (`true`/`false`/`1`/`0`). See [labels-and-control-signals.md](labels-and-control-signals/glossary-and-operations.md#question-auto-close) ([#9584](https://github.com/hivecommons/hive/issues/9584)). |
| `HIVE_QUESTION_AUTOCLOSE_HOURS` | No | `4` (config `governor.question_autoclose.hours`) | Hours an answered question stays open for the author to react 👎 before Hive closes it as completed. Non-positive or non-numeric values are ignored. |

## Credly badge integration (proposed — not implemented)
Expand Down
2 changes: 1 addition & 1 deletion src/docs/github-write-surface.md
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@ requires an `Origin` on its request and normalises labels through
upstream-watch, convergence channel) add their non-lane origin label themselves.
Provenance is never a gate: if a non-lane origin label cannot be ensured on the
repo the issue is still filed without it (logged as a warning), whereas a
retryable failure on a routing label keeps the request queued as before. See [labels-and-control-signals.md](labels-and-control-signals.md#origin-sources).
retryable failure on a routing label keeps the request queued as before. See [labels-and-control-signals.md](labels-and-control-signals/reference.md#origin-sources).

## Lane allowlist

Expand Down
2 changes: 1 addition & 1 deletion src/docs/hive-merge.md
Original file line number Diff line number Diff line change
Expand Up @@ -734,7 +734,7 @@ the planned set differs from the labels already on the PR, under the
`governor.labels.stage.enabled`. The mapping table, numbering rules, dwell
thresholds, the mermaid state machine and the off-happy-path flow
(072 → nudge → 074 → takeover) are in
[labels-and-control-signals.md](labels-and-control-signals.md#stage-labels-stagennn--the-pipeline-state-machine);
[labels-and-control-signals.md](labels-and-control-signals/stage-labels.md#stage-labels-stagennn--the-pipeline-state-machine);
the code is `src/pkg/stagelabels` and
`src/pkg/github/automerge/automerge_stage_labels.go`. Adoption
(`stage/074-adopted-by-hive`, `automerge_contributor_adopt.go`) reuses this
Expand Down
2 changes: 1 addition & 1 deletion src/docs/hive-open-issue.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ the relation survives a failed link. Once every child of `n` is closed the
issue stage sweep closes `n` as completed, and while any child is open `n`
is never marked `stage/stalled`
([#12857](https://github.com/hivecommons/hive/issues/12857); see
[labels-and-control-signals.md](labels-and-control-signals.md#decomposed-parents--closed-by-their-children-never-stalled)).
[labels-and-control-signals.md](labels-and-control-signals/stage-labels.md#decomposed-parents--closed-by-their-children-never-stalled)).

`--blocked-by <n[,n]>` records that the new issue must wait for issue(s) `n`
in the same repo, as GitHub "blocked by" dependencies
Expand Down
Loading
Loading