Performance logic updated

[marcusljf]

Summary by CodeRabbit

• Documentation
  • Updated performance bounties scope description to clarify that performance is tracked only after the bounty starts and that only revenue from new customers (whose first sale occurs after the bounty start) is counted.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cf7e211b-d645-406e-8cb1-d7330d1b9001

📥 Commits

Reviewing files that changed from the base of the PR and between 6ef9cc4 and ced5429.

📒 Files selected for processing (1)

• help/article/program-bounties.mdx

---

📝 Walkthrough

Walkthrough

The PR updates the "Scope" description in the performance bounties documentation to clarify that performance is tracked only after the bounty starts and specifies that counted revenue includes only customers whose first sale occurs after the bounty start date.

Changes

Performance Bounty Scope Documentation

Layer / File(s)	Summary
Scope clarification for performance bounties help/article/program-bounties.mdx	The "Scope" explanation for performance bounties is updated to clarify that performance tracking begins after the bounty start and that revenue is counted only from customers whose first sale occurs after the bounty start.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A bounty's scope now crystal clear,
Revenue counted from sales sincere,
After the start, performance we'll measure,
Customer first-buys bring bounty treasure! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Performance logic updated' is directly related to the main change in the changeset, which updates the performance bounty scope description to clarify how performance is tracked and revenue is counted.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bounty-performance-update

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Dub	🟢 Ready	View Preview	Jun 5, 2026, 4:14 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.