Funding issues

How to set scope and fund work effectively

Table of contents

To fund a task, paste the link to an existing GitHub issue and set a bounty. The issue itself is still where the work gets defined and discussed — Gitpay doesn’t replace that, it adds a bounty and a payment flow on top of it.

Write fundable issues

Good funded issues are:

  • Small enough to deliver
  • Unambiguous and testable
  • Clear about what is in/out of scope

A template for defining the task

Issues that are easy to fund — and easy for a contributor to pick up without back-and-forth — usually answer the same handful of questions:

  • Why this task. What’s the motivation? What happens once it’s done?
  • Level. Is this beginner, intermediate, or advanced? This helps the right contributor claim it.
  • Current behavior. What’s happening now, and how can someone reproduce it?
  • Expected behavior. What should happen instead once the change ships?
  • Useful links. Related issues, discussions, or references that add context.

Prefer acceptance criteria over assumptions

Add explicit criteria (bullet list), plus example inputs/outputs when possible.

Track progress in the repo

Ask contributors to submit work via Pull Request so you can review changes and see automated checks.

Where to go next