Quidli documentation
Visit websiteRead blogFollow us
  • What is Quidli?
  • Product overview
    • Web app
    • Discord
    • Slack
    • Telegram
    • GitHub
    • Farcaster
    • X (Twitter)
    • NFTs
    • Features
      • 🀝Send tokens
      • πŸ€–Automate token drops
      • 🎯Create reward flows
      • πŸ‘Send tokens via emojis
      • πŸͺ‚Airdrop tokens
      • πŸ‘©β€πŸ’»Incentivize dev work
      • πŸ’Recognize contributors with NFTs
  • Use cases
    • Internal team recognition
      • Welcome new team members
      • Recognize top performers & achievements
      • Celebrate special occasions
    • Community engagement
      • Monitor community dynamics via token transactions
      • Ensure your top contributors are being recognized
      • Leverage community to help boost your project on socials
    • Developer relations
      • Highlight specific issues to address on GitHub
      • Decrease support ticket resolution time
      • Keep hackathon participants engaged
  • FAQs
    • Questions
      • How does Quidli work?
      • Which tokens are supported on Quidli?
      • How are tx fees handled?
      • Can I withdraw tokens?
      • Can I get my token(s) added?
    • How can I contact you?
Powered by GitBook
On this page
  • How it works
  • General workflow
  • Closing a reward flow
  1. Product overview
  2. Features

Incentivize dev work

Create & offer developer-focused reward flows using GitHub Issues & Quidli

PreviousAirdrop tokensNextRecognize contributors with NFTs

Last updated 1 year ago

To create a GitHub reward flow, start by creating a GitHub Issue in your target repository.

Then copy your issue's public URL, head to the Quidli web app, create a GitHub Issues reward flow, and fill out all the relevant details including pasting in your issue URL.

How it works

General workflow

  1. Project manager creates issue as described above, resulting in the issue being displayed with a Quidli Reward Flow label on GitHub.

  2. Developer participates by making Pull Requests with their contributions.

  3. PM can validate a contribution for token rewards by accepting developer as an assignee.

  4. PM closes issue, triggering Quidli to update the reward flow and release token rewards to the accounts of approved assignees.

Closing a reward flow

When an issue is closed, Quidli will release the token rewards to each contributing assignee at the time of closing. Points to keep in mind:

  • As with other token reward flows on Quidli, you must commit the total amount you intend to distribute prior to launching your GitHub reward flow (ex. in order to set up 3 rewards of 100 USDC each, the max total of 300 USDC must first be locked up until your flow is closed.

  • Reward recipients are on a FIFO basis, so you won't be able to reward more assignees than you initially indicated when you set up the reward flow.

  • If you close the issue with less assignees than the number you initially set, then the remaining token rewards will be returned to your balance.

  • You can reject a contribution by simply not accepting accepting a developer's PR.

  • Once an issue is closed, the reward flow is finished. Reopening the issue on GitHub won’t restart it. If necessary, you can always create a new reward flow on reopened issues.

πŸ‘©β€πŸ’»
Once you've created a GitHub Issue in your target repository, use the Quidli web app to launch your GitHub token reward flow