Skip to content

L1 CI: traceability check should accept Refs/Updates/Resolves verbs #606

Closed

Description

@gHashTag

Problem

The L1 TRACEABILITY workflow (.github/workflows/l1-traceability.yml) only accepts Closes/Fixes #N but rejects Refs #N and Updates #N, which are standard GitHub linking verbs for incremental progress on the same epic issue.

Impact

PR #593 (the 3-month FGG676 SPI-flash unblock) has 8 commits using Refs #592 / Updates #592 as progress markers — they fail L1 even though they reference issue #592 correctly. This blocks merge of silicon-verified work.

Proposed fix

Accept the full canonical set:

  • Close(s) / Fix(es) / Resolve(s) — closes on merge
  • Ref(s) — references (work in progress)
  • Update(s) — progress update on existing issue

Fix in PR #605.

Activity

  1. added 3 commits that reference this issue on May 14, 2026
    62ec54a
    7137a87
    4b3ca9b
  2. added 2 commits that reference this issue on Jun 1, 2026
    f062d7e
    9464f50
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions