Skip to content

Partner referral rewards - #362

Merged
steven-tey merged 2 commits into
mainfrom
referral-reward
May 16, 2026
Merged

Partner referral rewards#362
steven-tey merged 2 commits into
mainfrom
referral-reward

Conversation

@marcusljf

@marcusljf marcusljf commented May 15, 2026

Copy link
Copy Markdown
Collaborator

Summary by CodeRabbit

Documentation

  • Added new Help Center article on partner referrals, explaining how referral attribution works and guiding users through configuring referral reward structures with percentage and flat-rate options.

Review Change Stack

@mintlify

mintlify Bot commented May 15, 2026

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated (UTC)
Dub 🟢 Ready View Preview May 15, 2026, 12:02 AM

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

@coderabbitai

coderabbitai Bot commented May 15, 2026

Copy link
Copy Markdown
Contributor

Warning

Rate limit exceeded

@steven-tey has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 59 minutes and 13 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ca024bb2-9c16-4932-8d43-78d65a3015b1

📥 Commits

Reviewing files that changed from the base of the PR and between bd8c47f and cdb0521.

⛔ Files ignored due to path filters (6)
  • images/dub-partners/referral-reward-commission.png is excluded by !**/*.png
  • images/dub-partners/referral-reward-default.png is excluded by !**/*.png
  • images/dub-partners/referral-reward-earnsatleast.png is excluded by !**/*.png
  • images/dub-partners/referral-reward-isapproved.png is excluded by !**/*.png
  • images/dub-partners/referral-reward-originalsale.png is excluded by !**/*.png
  • images/dub-partners/rewards-partner-referral.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • docs.json
  • help/article/partner-referrals.mdx
📝 Walkthrough

Walkthrough

This PR adds a Help Center navigation entry for a new partner referrals documentation article, registering it in docs.json under the "Engaging partners" section.

Changes

Partner Referrals Documentation

Layer / File(s) Summary
Navigation entry for partner referrals
docs.json
Added help/article/partner-referrals entry to the "Engaging partners" pages group in Help Center navigation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • dubinc/docs#351: Both PRs add new Help Center navigation entries and new partner-program MDX documentation pages under related analytics/partner topics, touching the shared docs.json navigation structure.
  • dubinc/docs#354: Both PRs modify help articles under help/article for partner features—this PR adds help/article/partner-referrals, while that PR updates help/article/partner-commissions (related within the same partner-earnings documentation area).

Suggested reviewers

  • steven-tey

Poem

🐰 A referral guide hops into view,
In the Engaging Partners crew,
Navigation finds its place so right,
Help Center shines ever bright! ✨

🚥 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 'Partner referral rewards' directly matches the main change, which adds documentation for partner referral rewards including setup and configuration details.
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 referral-reward

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

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@help/article/referral-rewards.mdx`:
- Line 17: Fix two typos in the referral rewards article: replace "the bring"
with "they bring" in the sentence "Partner referral rewards let you reward a
partner when another partner the bring on to your program meets a condition."
and change "referralreward" to "referral reward" wherever the concatenated term
appears (e.g., the string "referralreward") so the copy reads correctly.
- Line 65: The example sentence "For example, if you set a 10% referral reward
and the referred partner earns a $30 commission, the referring partner will earn
$3 as a referral reward. As well, the referred partner will earn a commission
based on the $30 in sales." is inconsistent; update it so both references use
the same base (either commission or sales). Specifically, change the second
clause to read that the referred partner's commission is based on the $30
commission (or alternatively change the first mention to "$30 in sales" and keep
the latter), ensuring the sentence consistently refers to the same amount; edit
the sentence containing the 10% example to keep terminology aligned.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7c767d14-c872-4650-89b5-d2d6f1806206

📥 Commits

Reviewing files that changed from the base of the PR and between bd8c47f and 812b737.

⛔ Files ignored due to path filters (6)
  • images/dub-partners/referral-reward-commission.png is excluded by !**/*.png
  • images/dub-partners/referral-reward-default.png is excluded by !**/*.png
  • images/dub-partners/referral-reward-earnsatleast.png is excluded by !**/*.png
  • images/dub-partners/referral-reward-isapproved.png is excluded by !**/*.png
  • images/dub-partners/referral-reward-originalsale.png is excluded by !**/*.png
  • images/dub-partners/rewards-partner-referral.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • docs.json
  • help/article/referral-rewards.mdx

Comment thread help/article/referral-rewards.mdx Outdated
Comment thread help/article/referral-rewards.mdx Outdated
@steven-tey

Copy link
Copy Markdown
Contributor

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented May 15, 2026

Copy link
Copy Markdown
Contributor
✅ Actions performed

Full review triggered.

@steven-tey
steven-tey merged commit 81730b3 into main May 16, 2026
4 checks passed
@steven-tey
steven-tey deleted the referral-reward branch May 16, 2026 00:26
This was referenced Jun 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants