Claiming Multiple Bounties: Multi-Bounty PRs
In this guide: Learn how to properly claim multiple bounties when working on several issues at once, avoid common pitfalls, and ensure you receive all your rewards.
Last updated
Was this helpful?
In this guide: Learn how to properly claim multiple bounties when working on several issues at once, avoid common pitfalls, and ensure you receive all your rewards.
Last updated
Was this helpful?
A multi-bounty situation occurs when you solve multiple issues that each have their own bounty rewards.
Important Rule: You must claim each bounty separately.
This means:
Think of it like separate transactions - each bounty payment needs its own dedicated PR to process correctly.
Lightning Bounties works with GitHub's automation system in a specific way:
When you add close #issue-number in a PR description, it signals the system to prepare a bounty payment
If you include multiple closure statements in one PR, the system may only recognize the first one
This means you could miss out on legitimate bounty payments for your work
Create a separate PR for each bounty issue you solve
In each PR description, include close #X, where X is the issue number
Merge each PR after review
This approach guarantees that each bounty is properly tracked and paid.
If you've already combined multiple fixes in a single PR:
Merge that combined PR as usual
For each additional bounty issue that wasn't properly claimed:
Create a minimal follow-up PR (e.g., update a comment or documentation)
Include close #X for the remaining issue in the PR description
Reference the original PR to explain the situation
Example:
Merge each follow-up PR to trigger the remaining bounty payouts
Lightning Bounties tracks rewards based on individual PR-to-issue relationships
The payment system processes each bounty claim independently
When multiple closure statements appear in one PR, the system typically only processes the first one
1. Solve multiple issues
Fix code for issues #10 and #12, each with a bounty.
2. Create PR for #10
PR description: close #10
3. Create PR for #12
PR description: close #12
4. Both PRs merged
Each bounty is automatically recognized and paid out by the system.
If you're ever unsure, default to one PR per bounty issue.
Always use the close #issue-number syntax in the PR description, not just in comments.
As shown in the image above, including multiple closes #issue-number lines in a single PR description may cause issues with the Lightning Bounties system.
Even though GitHub will close all the referenced issues, Lightning Bounties might only process the bounty for the first issue mentioned (#42 in this example), leaving you without the rewards for issues #57 and #63.
Always claim each bounty separately.
Use one PR per bounty issue whenever possible.
If you combine fixes, follow up with minimal PRs to close and claim each remaining bounty.
Use close #issue-number in each PR description to trigger the payout.
Creating a single PR that mentions multiple bounty issues won't properly trigger all payments
Lightning Bounties needs to see a clear one-to-one relationship between PRs and bounty issues
Every bounty issue needs its own dedicated "close #issue-number" statement
If you accidentally merged a PR that fixed multiple issues but only closed one bounty, create a new minimal PR for each remaining bounty, referencing the original PR as the source of the fix.
Keeping PRs atomic (one per issue) helps with clarity, review, and automation.
After removing or adding an issue link from the PR body, refresh the page to see the changes reflected in the PR interface. The previously linked issue will no longer appear in the related issues section.
Problem: You've already merged a PR that fixed multiple issues but only claimed one bounty Solution: Create minimal follow-up PRs for each unclaimed bounty, referencing the original PR
Problem: You're not sure if your PR will correctly trigger the bounty
Solution: Check that you've used exactly close #X, closes #X, or closed #X in the PR description (not in comments)
Problem: After editing a PR, you don't see changes to linked issues Solution: Refresh the page to see updated issue links in the PR interface
Check for the latest guidelines and best practices.
