Working on a Bounty

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.

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)

Example: Add a small comment or documentation update ⬇️

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