B9 — Integration test: tail-PR rebase watchdog fires within 60 s against fixture forge #445

Closed
opened 2026-04-27 10:01:12 +00:00 by dev · 0 comments
Collaborator

Follow-up from #425 / PR #436. The unit tests cover all dispatch-logic branches. This ticket tracks the integration test deferred because it requires a controllable Forgejo instance with real git state.

What is needed

  • A fixture forge (or in-process stub) with one open PR whose merge_base falls behind main.
  • The watchdog running for up to 60 s.
  • Assert that a rebase task is dispatched for that PR.

Why deferred

Setting up a fixture forge in CI requires creating a repo, pushing commits, opening a PR, and advancing main — substantial infrastructure that would block the core fix. Unit tests already cover every logic branch; this adds an end-to-end smoke check.

References

  • Issue #425 (original story)
  • PR #436 (implementation)
Follow-up from #425 / PR #436. The unit tests cover all dispatch-logic branches. This ticket tracks the integration test deferred because it requires a controllable Forgejo instance with real git state. ## What is needed - A fixture forge (or in-process stub) with one open PR whose `merge_base` falls behind `main`. - The watchdog running for up to 60 s. - Assert that a `rebase` task is dispatched for that PR. ## Why deferred Setting up a fixture forge in CI requires creating a repo, pushing commits, opening a PR, and advancing `main` — substantial infrastructure that would block the core fix. Unit tests already cover every logic branch; this adds an end-to-end smoke check. ## References - Issue #425 (original story) - PR #436 (implementation)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/claude-hooks#445
No description provided.