Add repository guidance to reviews safely

Ouverte
#160 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
54/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
docker, node.js, typescript

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
TypeScript
Étoiles
125
Forks
23
Merge moyen
2 j 13 h
PR mergées (30 j)
12

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de devarshishimpi/codra

Toutes les issues de devarshishimpi/codra

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.