After the merge: no second merge, no stuck card

A review card's pull request was merged. While its agent tidied up, it asked for permission to run a command. What the card's conversation showed then, and what it shows now.

Before

  1. 10:58Approved. Obeya merges PR #2.
  2. 10:58PR #2 merged. Live.
  3. 10:58Could not pull main after the merge …
  4. 10:58The agent asks for permission:rm -f …/.venv; rm -rf /tmp/… Allow / Deny
  5. 11:00The PR check runs again and takes the waiting card for an open PR: “Pull request merged. Live.” a second time
  6. 11:00Could not pull main after the merge … (again)
  7. 11:00The question disappears (“Left open”), but the agent still waits for its answer. The card shows “working”, nothing happens.
  8. 11:02Only Pause and Resume end the wait.

After

  1. 10:58Approved. Obeya merges PR #2.
  2. 10:58PR #2 merged. Live.
  3. 10:58Could not pull main after the merge … (once)
  4. 10:58The agent asks for permission:rm -f …/.venv; rm -rf /tmp/… Allow / Deny
  5. 11:00The PR check leaves the card alone: its pull request is merged already. No second merge, no second pull.
  6. laterThe question stays on the card until it is answered; then the agent goes on and finishes.

Also covered

If a pull request is merged (or a review card's pull request closed) while the agent waits for a permission, that call is now declined with the reason (“meanwhile your pull request was merged”). The agent continues and hears what happened, instead of waiting for a question that is no longer on the card.

Unchanged

The pull itself still follows the repository's own setting. With none set and a local main that has commits of its own, git refuses, as it did here; the card says so once.