Support Hackbot agents continuing after any action, not just a try push
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
From a discussion on PR #6531 (https://github.com/mozilla/bugbug/pull/6531#discussion_r3734810255): support continuing after a try push "or other action." Generalize action follow-up so an agent can resume after any recorded action it needs to wait on, such as a Phabricator review round or a Bugzilla needinfo response, not only a try push.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the discussion on PR #6531 and trace the existing try-push follow-up flow into the Hackbot action-recording and agent-resume entry points. Determine how a recorded action can represent waits for a Phabricator review round or Bugzilla needinfo response, and verify that agents resume after each supported action type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100