Skip to content

The shared Go validation runs twice on every pull request #6204

Description

@devantler

🤖 Generated by the Agentic Engineer (interactive Claude Code session)

Evidence

  • Every pull request here runs the organisation's shared Go validation twice on the same commit: once as the organisation-required workflow, and once more inside this repository's own CI, which calls the same workflow.
  • All 153 pull-request runs between 12 November 00:00 UTC and 13 November 11:00 UTC had both. The second copy used about 39 runner hours in those 35 hours: linting 17.5, coverage 9.6, tests 7.9, build 2.3, Go lint 1.4.
  • The second copy exists on purpose. The organisation rule applies only while GitHub detects this repository's main language as Go, and Go and Shell are close in size (6.80 MB against 6.29 MB today), so the rule could stop applying after any change. The in-CI copy guarantees a Go regression cannot merge if that happens.
  • The organisation's runner allowance was full during those hours, and production delivery waited on it (Production delivery stalls for hours when the organisation's runners are full #6203).

Problem

The repository pays for the same proof twice on every pull request, to insure against a rule that may one day stop selecting it.

Hypothesis

If the organisation rule selects this repository explicitly, and not by detected language, the in-CI copy protects nothing and can be removed. Every pull request then runs the Go validation once, with the same required result.

Acceptance criteria

  • The organisation rule that requires the Go validation selects this repository in a way that a change in detected language cannot undo. That rule is managed in devantler-tech/.github.
  • Read back from GitHub that the rule applies to this repository's default branch after that change.
  • Only then remove the in-CI copy, and keep the required check refusing a pull request whose Go validation did not succeed.
  • A check fails if this repository ever stops being covered by the organisation rule.
  • Before and after: runner hours of Go validation per pull request, from at least ten pull requests each.

Size

Small, in two steps across two repositories. The rule change must land and be read back first.

Part of #6203.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    Priority

    Medium

    Effort

    Low

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions