Skip to content

CI: diagnose failure of the contract-lint check itself (wayfinder #165, PR #157) #158

Closed

Description

@EthanThatOneKid

Summary

PR #157 introduces the contract-lint skill (skills/contract-lint — README.md, action.yml, lint.sh), and its own CI is failing: "CI: All jobs have failed," with the check dying in ~7 seconds with 3 annotations.

Because this PR introduces the lint, a fast failure like this points at the check/workflow setup (syntax error, missing input, script bug) rather than lint findings on existing code.

Evidence

  • CI failure notification: 2026-10-07 ~18:05 PT (GitHub notification email)
  • "CI: All jobs have failed" — check completed in ~7s, 3 annotations

Next steps

  • Pull the failure annotations from the workflow run and identify the root cause in the new action/lint.sh
  • Fix and re-run

Wayfinder #165 contract-lint rollout follow-up.

Activity

  1. EthanThatOneKid commented on Oct 11, 2026

    @EthanThatOneKid
    ContributorAuthor

    Resolved: #157 merged (2026-10-08), and the composite action now runs correctly. contract-lint passes on worlds-api PRs (#115, #119, #120 on 2026-10-10/11). It fails on wazoo-api#91 and wazoo-console#112 only because it correctly flags their deploy jobs, which haven't been converted to Infisical yet (Phase B of the CI/secrets map). That's a finding, not a defect.

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

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions