Lightning Bounties Documentation
Need Help? Join Our Discord!
  • 📖Lightning Bounties | Docs
  • Getting started
    • FIRST TIME ONBORDING
      • GitHub Auth & Lightning Bounties
    • SOLVING A BOUNTY
      • Finding Bounties to Solve
      • Working on a Bounty
      • Claiming Multiple Bounties: Multi-Bounty PRs
      • Claim Reward Criteria & Troubleshooting Guide
      • Withdrawing Funds
      • Working on Opensource Frontend: lb-next
      • How to Convert Sats into Local Currencies
    • POSTING A BOUNTY
      • Deposit Funds
      • Create a GitHub issue and Submit a new reward
    • MANAGING YOUR BOUNTY
      • Issue Lock Time
      • Add Reward to an Existing Bounty
      • Detach Issues from Pull Requests
      • Expire or Reclaim a Bounty Reward
      • User Balances Overview
  • ABOUT LIGHTNING BOUNTIES
    • Mission
    • Goals
    • Values
    • Features
    • Why Choose Lightning Bounties?
    • Lightning Bounties Team
  • Resources
    • Frequently Asked Questions
      • Lightning Bounties FAQ's
      • Lightning Network FAQ's
    • Glossary of Terms
      • Bitcoin & Lightning Terms
      • Lightning Bounties Terms
      • GitHub Terms
    • Social Media Channels
      • Website
      • Bounty Platform
      • Docs
      • Blog
      • Discord
      • GitHub
      • Twitter
      • Nostr
      • LinkedIn
      • YouTube
    • External resources
      • Satoshi in Bitcoin: What It Is and How Much It Is Worth
      • Use Lightning Network
      • GitHub issues
  • Contributing
  • LICENSE.md
  • CODE_OF_CONDUCT
Powered by GitBook
On this page
  • 1 - Look for an issue on the app.lightningbounties.com feed
  • 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
  • 3 - Create a Pull Request
  • 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:
  • 4 - Claim reward in app.lightningbounties.com
  • 4.1 - Click on "Claim Reward" and add pull requested number
  • 4.2 - Reward will be added to the balance

Was this helpful?

Edit on GitHub
Export as PDF
  1. Getting started
  2. SOLVING A BOUNTY

Working on a Bounty

Here you can find the steps to be taken to work on a bounty to get rewarded.

PreviousFinding Bounties to SolveNextClaiming Multiple Bounties: Multi-Bounty PRs

Last updated 1 month ago

Was this helpful?

1 - Look for an issue on the feed

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

2. Click the "..." button at the top-right of your PR description

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.

5. Click on "Update Comment"

# That's it!

This connects your PR to the issue and will trigger your bounty payment automatically.


ℹ️ Important Notes:

  • The closekeyword 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 closesyntax 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

2. Make a minimal change (can be as simple as updating documentation or adding a comment)

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

In this example, the colored logo has been added to the repo as requested.

Step 1
Step 2
Step 3
Step 4
Step 5

Example: Add a small comment or documentation update

4 - Claim reward in

⬇️
issue
app.lightningbounties.com
app.lightningbounties.com
'Add color to logo in this repo'
2. Click the "..." button at the top-right of your PR description
5. Click on "Update Comment"
4. Add close #[issue-number] to the PR description text
1. Go to your merged PR and Click Into It
3. Select "Edit"