dev/nisse
2
1 Fork 0
Code Issues 23 Pull Requests Actions Packages Projects Releases 1 Wiki Activity
338 Commits 2 Branches 1 Tag
0694b47c34f7452654796d050f723c217dd98f71
Commit Graph
3 Commits
Author SHA1 Message Date
dongarandClaude Opus 5.5 0694b47c34 nisse-dev: a settled reply posted top-level is no point to answer either
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 2m15s
Details
CI / e2e (pull_request) Successful in 5m6s
Details 
nisse-review's review of #169: a reply quoting a top-level point, or one
Gitea refused on its line, arrives through list_comments, so answering it
would start the thank-you loop again. Also records what the live Gitea
showed: resolving is per comment, and resolving again is a 204.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk
 2026-10-19 23:32:43 +00:00
dongarandClaude Opus 5.5 33d030590d nisse-review marks a reply that settles its thread; the PR's author resolves it
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m58s
Details
CI / e2e (pull_request) Successful in 7m41s
Details 
The reviewer is read-only (R3), so Gitea refuses it resolving a thread.
Now each reply says whether it settles its thread, and a settled reply
carries <!-- nisse-review: settled -->. nisse-dev, as the author, resolves
every comment on that thread's line when it watches the PR, and doesn't
take the settled reply as a point to answer. scripts/resolve_settled.py
does the same for PRs made by hand.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk
 2026-10-19 22:06:56 +00:00
dongarandClaude Opus 5.5 ecff719f1a M7.4: nisse-dev answers a peer
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 2m5s
Details
CI / e2e (pull_request) Successful in 3m30s
Details 
Anyone's comment on an item's PR but an operator's (and its own) is a
peer's point (D5, L11): kept on the item with an id, in the transcript as
a `peer` message labelled with its author, and never an instruction. The
driver answers each with answer_peer, inline on its line or quoting it,
or skips it with skip_peer and a recorded reason. A run going back to
waiting with points open is reminded once; then the harness lists them
on the PR. A peer's comment wakes the item; a wake by peers alone goes
back to the same wait quietly, with one line in the thread. The
operator's inline comments are now answered inline too.

Also corrects ci.yml's header: a push to main runs no end-to-end tests.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk
 2026-10-16 19:42:19 +00:00