Add repository guidance to reviews safely

Offen
#160 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
54/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
docker, node.js, typescript

Rechercherichtung

Start by reading issue #159 for how guidance files are found and matched, then trace where review context is assembled and how backend execution differs between Cloudflare Workers and Node/Docker. Add applicable guidance as clearly separated, size-limited context that cannot override review instructions, and keep reviews working when guidance is absent or skipped. Done means tests cover relevant, missing, and unsafe guidance, and typecheck, test, and lint commands pass.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement good first issue help wanted

Goal

Pass relevant repository guidance into the review so Codra can follow the team's conventions. Finding and matching files is handled in #159.

What to build

For each changed file, include the guidance that applies to its folder in the review context. Keep the guidance clearly separated from Codra's own review instructions. A review should still run when no guidance is available.

Safety

Treat guidance files as untrusted repository content. Use them only as context for reviewing code. They must not override Codra's rules, request secrets, or cause Codra to take actions outside the review. Keep the amount of guidance within the documented size limit.

Done when

  • Relevant guidance reaches the review for the changed files it covers.
  • Guidance cannot override Codra's instructions or request secrets.
  • Reviews work when guidance is missing or skipped.
  • Tests cover relevant guidance, missing guidance, and unsafe instructions.
  • Any backend changes work in both Cloudflare Workers and Node/Docker.
  • npm run typecheck, npm test, and npm run lint all pass.
Vorherrschende Sprache
TypeScript
Sterne
125
Forks
23
Ø Merge
2 T. 13 Std.
Gemergte PRs (30 T.)
12

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus devarshishimpi/codra

Alle Issues in devarshishimpi/codra

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.