GitHub OAuth blocked: user_not_whitelisted for @Jorel97

[Jorel97]

Hi CodeBounty team,

GitHub OAuth access for @Jorel97 has been blocked for several days with the CodeBounty error:

/auth/error?code=user_not_whitelisted

We also tried from a fresh browser/profile and got the same whitelist blocker, so this looks like an account/app whitelist issue rather than a local browser session problem.

Impact:

• Cannot access CodeBounty dashboard/apply flow.
• Cannot verify whether existing PRs are associated with CodeBounty tasks.
• Cannot safely apply to or work on new CodeBounty tasks while the whitelist blocker is active.

Could you please whitelist @Jorel97 or let us know the correct onboarding/support path to restore CodeBounty access?

For now we are pausing all new CodeBounty task work until login/apply access is restored.

Thanks.

[Jorel97]

Update: I tried the public support email listed for the older CodeBounty GitHub org (support@codebounty.co), but the message bounced with “address not found”, so that support channel appears to be unavailable.

I also tested the new claim flow at:

https://www.codebounty.org/claim

Using this bounty issue URL:

#1

The claim page accepts/parses the GitHub issue URL, but returns “No Claimable Bounties” even though the issue publicly shows a CodeBounty bounty and bot-generated bounty links, including:

https://dev.codebounty.ai/bounty/6a14bf3c3412ad1040b881c5

Related PR from @Jorel97:

#37

Could you confirm the correct support channel and whether this is expected because claims only become available after PR merge, or whether the legacy dev.codebounty.ai bounties need migration/whitelisting for the new codebounty.org claim flow?

[Jorel97]

Hi CodeBounty team,

Following up on this blocker for @Jorel97.

Could you please confirm three things?

1. Whether @Jorel97 can be whitelisted for GitHub OAuth / dashboard access.
2. Whether existing legacy dev.codebounty.ai bounty PRs can be claimed or associated through the current codebounty.org/claim flow.
3. Whether real Stripe payouts are currently enabled for contributors, or whether the platform is still limited to test Stripe accounts.

Current impact is unchanged: we cannot safely apply to new CodeBounty tasks, verify PR association, or count these bounties as payable until OAuth/claim/payout status is confirmed.

Relevant existing PRs from @Jorel97 in this repo include #37, #38, #39, #40, and #41.

Thanks.