Skip to content

Acceptance harness cross-check filters the discovery path the same way the range does #242

Description

@sameera

Make the acceptance harness's GitHub file-list cross-check exclude the discovery directory, so a pull request that touches discovery prose is not reported as a range mismatch.

Meta

The range the distiller recomputes already excludes the discovery directory alongside the queue, in the git-diff based helpers. The harness's own cross-check filters GitHub's file list by string prefix instead, and it still strips only the queue path. An acceptance run against a pull request that touches discovery prose therefore reports a file-set mismatch that is not a real mismatch. The check is advisory today, so the failure is a misleading report rather than a wrong result.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogepicEpic (created by nxs-gh-create-epic)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions