Dashboard › publish › Session 1111R8cXIwq3
1111R8cXIwq3gbm9fPerform an independent adversarial correctness review of the current uncommitted approval-gate changes in /home/byk/Code/getsentry/publish. Do not edit files. Inspect the full workflow integration, source scripts, and tests. Focus specifically on whether approval remains bound to the exact target/title/event across automatic approvals, ci-poller, ci-ready, and publish; failure cleanup; GitHub Actions expression semantics; pagination/API semantics; and workflow_dispatch behavior. Check for regressions in supported Publish title grammar. Return substantive findings only, each with severity (MUST-FIX/HIGH/MEDIUM/LOW/CONCERN/PASS), exact file:line references, evidence and fix recommendation. End your response with exactly MERGE or DO-NOT-MERGE. Do not use background work.
<skill_content name="jj-guide"> # Skill: jj-guide # jj Guide for AI Agents Jujutsu (jj) is a Git-compatible VCS with mutable commits, automatic snapshotting, no staging area, and first-class conflicts. This skill teaches you how to use it safely from a non-interactive agent environment. If `.jj/` exists in the repo root, this is a jj repo. **Use `jj` commands, not `git`.** In a colocated repo (`.jj/` *and* `.git/`), git tools can read the state, but mutations should go through `jj` so the operation log stays consistent. ## Critical Rules - **NEVER** use interactive flags (`-i`, `--interactive`). TUI prompts hang in agent environments. This applies to `jj split -i`, `jj squash -i`, `jj commit -i`, `jj resolve`, `jj diffedit`, etc. - **ALWAYS** pass `-m "msg"` when describing/committing. Without `-m`, an editor opens and hangs. - **VERIFY** mutations with `jj st` and `jj log` after `squash`, `abandon`, `rebase`, `restore`, `commit`. ...