4. Open a PR

What you’ll do: Open a pull request that closes the bounty issue, so a merge triggers your payout.

Two things must be true for the payout to fire on merge: the PR body links the issue, and you (the assignee) are the PR author.

Link the issue in the PR body

TOSS matches a merged PR to its bounty by parsing the PR body for a closing keyword and issue number.


Closes #123

Fixes #123 and Resolves #123 work too (and their past-tense variants). Put it in the PR description, not just a commit message.

No closing reference in the PR body means TOSS can’t link the PR to the bounty, and merging won’t release anything. Double-check Closes #<issue> is in the description before you request review.

Author must be the assignee

The merge-time check compares the PR author’s GitHub ID to the assigned contributor’s. If they differ, the bot aborts the payout and comments. If you’re pairing or someone else pushed the branch, make sure the PR is opened by the assigned account.

Open it

Push your branch

Commit your work and push to your fork or branch.

Open the PR

Target the repo’s default branch. In the description, add Closes #<issue>.

Fill in the description

Explain what changed and how you verified it — standard review hygiene. The maintainer reviews as usual.

Done when

Your PR is open, authored by your assigned account, with Closes #<issue> in the description. Now it’s on the maintainer to review and merge.

Next: Get paid · Stuck? Troubleshooting