GithubWebhooksService.handlePullRequest never reacts to a PR being opened — markInReview only ever fires synthetically at merge time

[chonilius]

handlePullRequest() returns [] immediately unless payload.action === 'closed' && payload.pull_request.merged — i.e. it does nothing at all for a PR-opened (or reopened, synchronize, etc.) webhook event. BountiesService.markInReview(id, prUrl, prNumber) exists specifically to transition a bounty CLAIMED -> IN_REVIEW when a PR is opened against its issue, but the only place it's ever called is inside handlePullRequest's merged-PR branch, immediately before markMergedAndRelease — i.e. markInReview only ever fires in the same instant as a merge, never in response to the actual "a PR was opened" event that should trigger it.

Practical consequence: a contributor who opens a PR that sits open for review (the common case) never sees their bounty move to IN_REVIEW from the webhook's perspective — it stays CLAIMED in the database (and in any UI reading Bounty.status) right up until the PR is merged, at which point IN_REVIEW and MERGED both happen within the same request. This is distinct from the already-filed issue about a PR closed without merging having no handler — this is about PRs that are opened (merged or not) having no handler either. Add a case for action === 'opened' (and arguably 'reopened') that resolves the linked bounty and calls markInReview at the time the PR is actually opened.

[Syringe7]

I would love to work on this issue. please assign to me to work on it ASAP

[probablyABug]

@probablyABug has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

hi, i would like to work on this.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @probablyABug to this issue.

[Wiseman52]

@Wiseman52 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’m confident I can take ownership of this task and deliver a well-tested solution that meets your expectations.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Wiseman52 to this issue.

[codefather2026]

@codefather2026 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer, i will like to solve this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @codefather2026 to this issue.

[Jaydbrown]

@Jaydbrown has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

hello maintainer, i would love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jaydbrown to this issue.

[drips-wave]

Congratulations, @Jaydbrown! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Jaydbrown: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊