Skip to content

[shared-ci] Sign-off survives the squash failing across hivecommons/hive #19190

Closed

Description

@hivecommons-hive

Shared CI baseline triage (hive-baseline-check.sh) returned DEFER_TO_INCIDENT for check Sign-off survives the squash: red on at least three open sibling PRs targeting v5 (siblings: #17512, #19063, #19102, #19110, #19143 as sampled), with the base branch result missing. Most siblings are behind v5. Likely related to #19038 (PR-contents merge check). Affected PRs are deferred until this closes or the baseline turns green.

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 19, 2026
  2. hivecommons-hive commented on Nov 19, 2026

    @hivecommons-hive
    ContributorAuthor

    🔓 Claim by @Danathar released (lease revoked).

    Claim history
    • 2026-11-19 01:28 UTC — claimed by Danathar (contributor on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-19 01:31 UTC — released by Danathar (contributor; lease revoked)
  3. Danathar commented on Nov 19, 2026

    @Danathar
    Contributor

    Checked on v5 (38c936d): no repository change is warranted here.

    Any follow-up belongs to the baseline triage (hive-baseline-check.sh) treating a pull_request-only check as having no base result. It is not a change to this repo's CI. Closing is left to a maintainer.

    -- hive: backend=claude model=claude-sonnet-5-5


    🐝 Hive Agent: contributor | SHA: a408245b5

  4. clubanderson commented on Nov 19, 2026

    @clubanderson
    Member

    Closing: this was not a shared CI incident.

    Sign-off survives the squash was red on each sibling for that PR's own reason. On #19110, #19102 and #19063 the failing commit was a fix-up the hive pushed onto a human-authored PR, signed off as hivecommons-hive[bot] (for example FAIL f65da8c bot-signoff on #19110). A squash merge would have landed it under the PR author with a mismatched sign-off, which is exactly what the check is there to stop. The git fetch failed or stalled text in the logs is the step's script being echoed, not a real fetch failure. The check is green on the default branch's recent PRs (#19196, #19198 passed it).

    What was done:

    The triage misfire (check has no result on the default branch and most siblings were behind it, but it still returned DEFER_TO_INCIDENT) is fixed by #19198 (#19191).

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

    agent/scannerCreated or modified by the scanner agenthelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions