Add repository guidance to reviews safely

Abierto
#160 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
54/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, node.js, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
TypeScript
Estrellas
125
Forks
23
Merge medio
2 d 13 h
PR fusionados (30 d)
12

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de devarshishimpi/codra

Todos los issues de devarshishimpi/codra

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.