[repo-assist:issue-triage] githubnext/gh-cao issue 17797 triage guidance

Open Beginner friendly
  • Is something wrong?
#20,041 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, markdown
Domain
ci-cd

Research direction

Open .github/workflows/eu-cra-compliance-scope-classifier.md around lines 136-175 and add the explicit instruction for Regulation (EU) 2025/1535. Update the CRA-ACTS-006 row in eu-cra-compliance/implementation-status.md. Run npm run compile and npm run compile:locks; done means compile passes and ledger shows gap closed.

Written by the indexing model from the issue text.

Description

repo-assist repo-assist:issue-triage

Target githubnext/gh-cao issue 17797 (CRA-ACTS-006) describes a real, bounded gap: the scope-classifier prompt only requires generic "applicable delegated acts" discovery and never names Delegated Regulation (EU) 2025/1535 (Regulation (EU) No 168/2013 products). Confidence: high. No open PR tracks it.

Action: A maintainer should assign githubnext/gh-cao issue 17797 to Copilot with the prompt below; acceptance: npm run compile passes, the prompt keeps the human-review gate, and the ledger row CRA-ACTS-006 is updated.

Evidence
  • .github/workflows/eu-cra-compliance-scope-classifier.md (~lines 136-175): source hierarchy lists "Applicable delegated acts" generically; no mention of 2025/1535 or 168/2013 (the act appears only in the ledger).
  • eu-cra-compliance/implementation-status.md line 85: CRA-ACTS-006 is PARTIAL with exactly this gap; primary-text verification is INCOMPLETE.
  • The classifier already says missing evidence does not establish exclusion and requires human review, so the change is additive.
  • Open PR search for CRA-ACTS-006 / 2025/1535: none.
Agent prompt

In .github/workflows/eu-cra-compliance-scope-classifier.md, add an explicit instruction to check and cite Commission Delegated Regulation (EU) 2025/1535 ((eurlex.europa.eu/redacted) when a candidate repository may map to products within the scope of Regulation (EU) No 168/2013. Keep it evidence-only: require human review for any claimed exclusion, never declare a repository out of scope autonomously, and report inaccessible or ambiguous evidence as INCOMPLETE or HUMAN_REVIEW_REQUIRED. Update the CRA-ACTS-006 row in eu-cra-compliance/implementation-status.md to match. Run npm run compile and npm run compile:locks; do not edit .lock.yml files by hand.

Control Plane

cao: githubnext/gh-cao, correlation: 41228535215-121

Generated by 🏷️ Repo Assist / Issue Triage · copilot · auto · ~22 AIC · ⌖ ~1 AIC · ⊞ 14K · ◷

  • expires on Nov 14, 2026, 6:25 PM UTC
Dominant language
JavaScript
Stars
14
Forks
5
Avg merge
3h 24m
Merged PRs (30d)
796

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-cao

All issues in githubnext/gh-cao

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.