fmt: clippy doc_markdown backticks

This commit is contained in:
müde 2026-05-15 23:11:10 +02:00
parent edb0108ae7
commit fc61cb9310
4 changed files with 13 additions and 13 deletions

View file

@ -127,16 +127,16 @@ fn finish_approval(
result
}
/// Tag-driven ApplyCommit handler. Walks the approval through the tag
/// state machine documented in `docs/approvals.md`: stamp `approved/<id>`
/// + `building/<id>` first so the audit trail captures intent, then
/// drop the candidate tree into the working dir without moving HEAD,
/// run the rebuild, and either fast-forward `applied/main` to the
/// proposal commit on success (`deployed/<id>`) or annotate
/// `failed/<id>` with the build error and reset the working tree back
/// to the last known-good main. main never advances on a failed
/// build, so a crash-and-recover doesn't leave the agent pointing at
/// a tree it can't evaluate.
/// Tag-driven `ApplyCommit` handler. Walks the approval through the tag
/// state machine documented in `docs/approvals.md`: stamp
/// `approved/<id>` and `building/<id>` first so the audit trail
/// captures intent, then drop the candidate tree into the working dir
/// without moving HEAD, run the rebuild, and either fast-forward
/// `applied/main` to the proposal commit on success
/// (`deployed/<id>`) or annotate `failed/<id>` with the build error
/// and reset the working tree back to the last known-good main. main
/// never advances on a failed build, so a crash-and-recover doesn't
/// leave the agent pointing at a tree it can't evaluate.
async fn run_apply_commit(
coord: &Arc<Coordinator>,
approval: &hive_sh4re::Approval,

View file

@ -42,7 +42,7 @@ fn ensure_kind_column(conn: &Connection) -> Result<()> {
}
/// Same shape as `ensure_kind_column` but for `fetched_sha` — the
/// canonical sha hive-c0re vouched for at request_apply_commit time.
/// canonical sha hive-c0re vouched for at `request_apply_commit` time.
/// Distinct from `commit_ref` (manager-supplied, may not even resolve
/// in proposed by the time we approve).
fn ensure_fetched_sha_column(conn: &Connection) -> Result<()> {

View file

@ -470,7 +470,7 @@ async fn git(dir: &Path, args: &[&str]) -> Result<()> {
}
/// Fetch `sha` from the `src` git repo into `dst` and pin it as
/// `refs/tags/<tag>`. Used at request_apply_commit time so hive-c0re
/// `refs/tags/<tag>`. Used at `request_apply_commit` time so hive-c0re
/// captures an immutable handle on the manager's commit; subsequent
/// amendments / force-pushes in `src` no longer affect what gets
/// built. Returns the resolved sha (which equals `sha` on success

View file

@ -281,7 +281,7 @@ pub enum HelperEvent {
/// Sha that ended up at `deployed/<id>` on success, or the
/// proposal sha that just got tagged `failed/<id>` on
/// failure. None for the (rare) rebuild path that doesn't go
/// through an approval (e.g. auto_update::rebuild_agent
/// through an approval (e.g. `auto_update::rebuild_agent`
/// reapplying the existing main).
#[serde(default, skip_serializing_if = "Option::is_none")]
sha: Option<String>,