In this example, we are using:
1.1 - Click on the issue to get details
1.2 - Click on 🔗 to see the issue in GitHub
2 - Fix the issue
2.1 - Fork the owner repo to your repository
2.2 - Work on the issue
This is the part where developers work on fixing the code after they fork the repo. 🧑💻
3 - Create a Pull Request
Create a pull request to the bounty poster repo.
3.1 - Close the issue you fix on the Pull Request description
⚠️ Note: This step is crucial⚠️
If you forget to add the tag close #(issue-number)
, & the PR is already merged.
You have 2 options:
[1] Edit the Pull Request Message
We got you covered! 👇
1. Go to your merged PR and Click Into It
3. Select "Edit"
4. Add close #[issue-number] to the PR description text
Example: If fixing issue #5
, add close #5
to your PR description.
# That's it!
This connects your PR to the issue and will trigger your bounty payment automatically.
ℹ️ Important Notes:
The close
keyword must be in the PR description itself, not in regular comments.
Adding this connection after merging will automatically trigger the lightning bounty payment.
If you cannot edit the PR, ask the repo owner to add the close
syntax for you.
[2] Creating a New Pull Request When You Forgot to Add close #issue-number
If your original pull request has been merged but you forgot to include the close #issue-number
syntax needed for Lightning Bounties payment:
Steps to Create a New PR
1. Create a new branch from the current main/master branch
git checkout main
git pull
git checkout -b fix-bounty-issue-reference
git add .
git commit -m "Add reference to close issue #X for Lightning Bounty"
3. Push your branch
git push origin fix-bounty-issue-reference
4. Create the new pull request
Go to the repository on GitHub
Click "Compare & pull request"
Important: Include close #X
or closes #X
in the PR description (where X is your issue number)
Explain that this PR is to properly close the issue for Lightning Bounty payment
Reference your original PR: "This PR references the work completed in #Y"
ℹ️ Important Notes:
The repository owner will need to review and approve this new PR
This is a technical solution to trigger the Lightning Bounties payment system
The minimal change is necessary as GitHub requires actual content changes for a PR
Once the Pull Request gets approved, the developer can claim the reward
4.1 - Click on "Claim Reward" and add pull requested number
4.2 - Reward will be added to the balance