Skip to content

Fix: Update config documentation details#102

Open
aviisharma238 wants to merge 1 commit into
yashdev9274:mainfrom
aviisharma238:ai-fix-issue-4
Open

Fix: Update config documentation details#102
aviisharma238 wants to merge 1 commit into
yashdev9274:mainfrom
aviisharma238:ai-fix-issue-4

Conversation

@aviisharma238

@aviisharma238 aviisharma238 commented Jun 12, 2026

Copy link
Copy Markdown

This Pull Request was autogenerated by the Avii OSS AI Agent platform.

Issue Description

Config details inside README are outdated. Update deployment details.

Resolution Details

  • Automated fix generated using Gemini 1.5 Flash
  • Built and validated inside isolated agent workspace

Summary by CodeRabbit

  • Documentation
    • Enhanced configuration and OAuth setup documentation with clearer guidance on production URL requirements for environment variables and GitHub OAuth callback configuration.

@vercel

vercel Bot commented Jun 12, 2026

Copy link
Copy Markdown

@aviisharma238 is attempting to deploy a commit to the yashdev9274's projects Team on Vercel.

A member of the Team first needs to authorize it.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown

Review Change Stack

Walkthrough

This PR updates the README.md documentation to clarify BETTER_AUTH_URL configuration requirements for both local development and production deployment. The same guidance is expanded across three related sections: the environment setup example, the GitHub OAuth callback instructions, and the environment variables reference table.

Changes

Configuration Documentation Update

Layer / File(s) Summary
BETTER_AUTH_URL production guidance
README.md
Environment variable setup section, GitHub OAuth callback section, and required environment variables table all expanded with inline instructions distinguishing local development URLs from deployed/production domain URLs for BETTER_AUTH_URL configuration.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Configuration clarity blooms today,
Dev and prod URLs light the way,
OAuth flows know where to go,
Production domains now clearly show!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Fix: Update config documentation details' is vague and overly generic, using non-specific terms like 'details' that don't clearly convey the specific changes made to the documentation. Consider using a more specific title that describes the actual changes, such as 'Update README with production URL guidance for BETTER_AUTH_URL and OAuth configuration' to better communicate the scope of updates.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
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

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

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 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 `@README.md`:
- Line 240: The README currently instructs users to substitute their deployed
domain for the GitHub OAuth callback, but the code in
apps/supercode-cli/server/src/lib/auth.ts hardcodes
https://supercode-terminal.vercel.app/api/auth/callback/github; update either
the README to show the exact production callback URL
(https://supercode-terminal.vercel.app/api/auth/callback/github) or, preferably,
modify auth.ts (look for the hardcoded callback constant or function that builds
the callback URL, e.g., AUTH_CALLBACK_URL or getCallbackUrl) to read the
callback from an environment variable (e.g., NEXTAUTH_URL or
GITHUB_CALLBACK_URL) and document that env var in the README so the runtime and
docs match.
🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 96c0a571-6520-4867-b9da-b4c480865ed6

📥 Commits

Reviewing files that changed from the base of the PR and between d0cc610 and ef31431.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
1. Go to [GitHub Developer Settings](https://github.com/settings/developers)
2. Create a new OAuth App
3. Set Authorization callback URL: `http://localhost:3000/api/auth/callback/github`
3. Set Authorization callback URL: `http://localhost:3000/api/auth/callback/github` (for local development). In production, use your deployed domain, e.g., `https://your-app.com/api/auth/callback/github`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Use the exact production callback URL here.

The current runtime hardcodes https://supercode-terminal.vercel.app/api/auth/callback/github in apps/supercode-cli/server/src/lib/auth.ts, so telling users to substitute any deployed domain will break GitHub OAuth unless the code is changed too.

Suggested edit
-3. Set Authorization callback URL: `http://localhost:3000/api/auth/callback/github` (for local development). In production, use your deployed domain, e.g., `https://your-app.com/api/auth/callback/github`.
+3. Set Authorization callback URL: `http://localhost:3000/api/auth/callback/github` (for local development). In production, use `https://supercode-terminal.vercel.app/api/auth/callback/github` unless `apps/supercode-cli/server/src/lib/auth.ts` is updated to derive this from `BETTER_AUTH_URL`.
🤖 Prompt for 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.

In `@README.md` at line 240, The README currently instructs users to substitute
their deployed domain for the GitHub OAuth callback, but the code in
apps/supercode-cli/server/src/lib/auth.ts hardcodes
https://supercode-terminal.vercel.app/api/auth/callback/github; update either
the README to show the exact production callback URL
(https://supercode-terminal.vercel.app/api/auth/callback/github) or, preferably,
modify auth.ts (look for the hardcoded callback constant or function that builds
the callback URL, e.g., AUTH_CALLBACK_URL or getCallbackUrl) to read the
callback from an environment variable (e.g., NEXTAUTH_URL or
GITHUB_CALLBACK_URL) and document that env var in the README so the runtime and
docs match.

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.

1 participant