You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Move the comment reaction to Python, tested against the stub #16
The 👀 reaction on a comment command becomes tested Python. The react job's step is rewritten in standard-library Python, inline in the reusable workflow, and tested against the stub harness from the membership lookup ticket.
Acceptance criteria
Behaviour is unchanged: the comment id must be all digits before it is used; HTTP 200 and 201 count as success; any other answer, a timeout or a connection failure gives a warning annotation and never a red check.
The job's token is sent as a header set in the program, never on a command line or in output.
The job's permission stays issues: write only.
Unit tests cover 200, 201, 403, 404, timeout, connection failure and an invalid comment id.
Plan change (2026-11-18): this is implemented inside the open stack instead of after the release, so no code is merged only to be replaced. It lands on #12's branch and is merged up the stack.
Follow-up: #20 moves this step's code from the workflow file into a Python file the workflow checks out at its own commit (tickets #21–#27). Behaviour and tests stay the same; only where the code lives and how the tests find it change.
Activity
cipherstash-agent commentedon Nov 18, 2026
Plan change (2026-11-18): this is implemented inside the open stack instead of after the release, so no code is merged only to be replaced. It lands on #12's branch and is merged up the stack.
Generated by Claude Code
refactor: move the routine call to Python so every answer is tested
test(react): characterise the reaction step through the harness
refactor(react): move the 👀 reaction to Python so every answer is tested
Merge feat/comment-command into feat/requested-reviewer
fix: harden the reaction step as the other request steps are
cipherstash-agent commentedon Nov 18, 2026
Follow-up: #20 moves this step's code from the workflow file into a Python file the workflow checks out at its own commit (tickets #21–#27). Behaviour and tests stay the same; only where the code lives and how the tests find it change.
Generated by Claude Code