Skip to content

Waiting lines in CI watch and Self-merge #814

Closed

Description

@JacobStephens2

Parent

#776

What to build

Stages that wait on something else, CI watch and Self-merge, write a line to the Command log at least every logs.waiting_line_minutes (5 by default) while they wait, even when nothing has changed. For example: "CI on f7c3940: 3 still running out of 17 checks". Today CI watch writes a line only when the count of running checks changes, so a long CI run can go 10 minutes without one and would read as Silent. The new setting is in the User config's [logs] section.

Acceptance criteria

  • While CI watch waits on checks that stay running, a waiting line is written at least every logs.waiting_line_minutes, as well as whenever the count changes.
  • Self-merge writes waiting lines the same way while it waits.
  • logs.waiting_line_minutes is read from the User config and defaults to 5.
  • A Command log line is still written whenever the count changes, as now.
  • Tested through the binary against the fake GitHub, with checks that stay running.

Activity

  1. JacobStephens2 commented on Oct 19, 2026

    @JacobStephens2
    OwnerAuthor

    Closed by #841, merged into issue-776 by a thirdshift Merge run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions