dev/nisse

1 Fork 0

Files

T

History

dongarandClaude Opus 5.5 e107484042

CI / checks (push) Skipped

CI / checks (pull_request) Successful in 1m55s

Details

CI / e2e (pull_request) Successful in 3m56s

Details

nisse-review: a commit diff Gitea can't give falls back to the whole diff

From nisse-review's review of #156: only a failed listing fell back to
the PR's whole diff; one commit's diff failing (a force-push dropped it)
failed the run. Tests also pin down its other three points, which the
code already handled: a command is taken in once, a second review at the
same head has its own marker, and `review` beside a comment is one fresh
review.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk

2026-10-17 07:47:48 +00:00

src/nisse_review

nisse-review: a commit diff Gitea can't give falls back to the whole diff

2026-10-17 07:47:48 +00:00

tests

nisse-review: a commit diff Gitea can't give falls back to the whole diff

2026-10-17 07:47:48 +00:00

pyproject.toml

M7.3: nisse-review's first slice

2026-10-13 22:34:02 +00:00

README.md

M7.3: nisse-review's first slice

2026-10-13 22:34:02 +00:00

README.md

nisse-review

The Review Agent (Part R of the architecture): it reviews every pull request that is ready, in the repositories its Gitea account can read, and posts its review on the PR as a COMMENT review. It reads and comments; it never changes code, approves, or requests changes.

A thin application over nisse-core, with its own small scheduler:

config: its YAML configuration (nisse-review.example.yaml).
state: its state store, and a review item (one per PR).
scheduler: the duty (ready PRs), one review at a time, recovery after a crash.
reader: the repository at the PR's head and base, read-only, from Gitea's archives: the run's executor.
review: one review run, and posting it.
build, main: putting it together, and the access check at startup.

Bring-up on the development VM: scripts/review-bringup.sh.