Add actionable commands to pull request comments

Offen
#152 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
45/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github, typescript

Rechercherichtung

Start with the pull request comment handler that turns configured mentions into review jobs, then read the existing review category and repository settings code. Issues #155 and #156 split command parsing and finding responses into separate work; inspect those before choosing a slice. Done means supported commands and invalid-command replies work with configured mentions, existing full reviews still work, and tests, docs, typecheck, and lint cover the changed behavior across affected runtimes.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement good first issue help wanted

Goal

Let developers ask Codra to do different things from a pull request comment. Today, a new comment that contains the configured Codra mention starts the same full review, regardless of the rest of the comment.

What should change

Support a small set of clear commands after the configured mention:

  • @codra-app review starts a full review.
  • @codra-app review focus correctness reviews one supported category. The user can choose any category Codra already supports.
  • @codra-app explain <finding> explains a finding.
  • @codra-app address <finding> suggests a way to fix a finding in a reply.

The examples use @codra-app, but commands must also work with the mention trigger configured for that repository. The address command suggests a change only. Codra must not edit files, push commits, or make changes to a branch.

Current behavior and context

Codra handles GitHub pull request comments and turns a matching mention into a review job. It does not currently interpret command words after the mention. Review categories and repository settings already exist, so reuse those instead of adding a new category or a separate security command.

Work breakdown

Done when

  • Supported commands are recognized after the repository's configured mention.
  • Existing mention based full reviews continue to work.
  • Invalid or incomplete commands receive a short, useful response.
  • The commands and examples are documented.
  • Tests cover command parsing and the resulting behavior.

Before closing

  • npm run typecheck, npm test, and npm run lint all pass.
  • Any backend changes work in both Cloudflare Workers and Node/Docker.
  • Tests cover the changed behavior in each affected runtime.
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.