Skip to content

Remove the stale triage copy that shadowed cra-gates - #28

Merged
bhupenderverma-cybertec merged 1 commit into
mainfrom
fix/stale-triage
Sep 8, 2026
Merged

bhupenderverma-cybertec merged 1 commit into
mainfrom
fix/stale-triage

Conversation

@bhupenderverma-cybertec

Copy link
Copy Markdown
Collaborator

Run 76 of cra-triage-main showed the traceback coming from this repository's own triage/ folder, not from .cra-gates/: python -m triage found the old copy first. The copy, its tests and the old scoring table go; both workflows move to cra-gates fc3ff8b, whose triage steps set PYTHONSAFEPATH so this cannot happen again anywhere. TRIAGE.md now points at the shared code.

Run 76 of cra-triage-main showed the traceback coming from this
repository's own triage/ folder, not from .cra-gates/: python -m triage
found the old copy first. The copy, its tests and the old scoring table
go; both workflows move to cra-gates fc3ff8b, whose triage steps set
PYTHONSAFEPATH so this cannot happen again anywhere. TRIAGE.md now points
at the shared code.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown

CRA triage

No findings on this pull request head.

@cybertec-ogtay
cybertec-ogtay self-requested a review September 8, 2026 08:57

@cybertec-ogtay cybertec-ogtay left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved.

@bhupenderverma-cybertec
bhupenderverma-cybertec merged commit b731c22 into main Sep 8, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants