Skip to content

Fix typo in authentication FAQ section#1099

Merged
msukkari merged 1 commit intosourcebot-dev:mainfrom
wschoot:patch-1
Apr 8, 2026
Merged

Fix typo in authentication FAQ section#1099
msukkari merged 1 commit intosourcebot-dev:mainfrom
wschoot:patch-1

Conversation

@wschoot
Copy link
Copy Markdown
Contributor

@wschoot wschoot commented Apr 8, 2026

Summary by CodeRabbit

  • Documentation
    • Fixed typos and formatting in the authentication FAQ to improve clarity and readability.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 8, 2026

Walkthrough

Fixed a spelling error in the FAQ documentation by correcting "credientials" to "credentials" and ensured the file ends with a newline. No structural or content changes were made to the documentation.

Changes

Cohort / File(s) Summary
Documentation Typo Fix
docs/docs/configuration/auth/faq.mdx
Corrected misspelling of "credentials" and added newline at end of file.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title accurately describes the main change: fixing a typo ('credientials' to 'credentials') in the authentication FAQ section.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ 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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

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 the current code and only fix it if needed.

Inline comments:
In `@docs/docs/configuration/auth/faq.mdx`:
- Line 39: Update the sentence containing "(credentials, Google, GitHub, etc)
and an interface to enable user registration and log in. Internally, Auth.js
uses JWT to provide" by wrapping the technical provider names and values in
inline code formatting (e.g., `credentials`, `Google`, `GitHub`, `JWT`) so they
follow the docs style; keep the surrounding punctuation and wording unchanged
and ensure only the provider/technical tokens are converted to inline code.
- Line 44: Replace the closing CTA sentence "Have a question that's not answered
here? Submit an issue on
[GitHub](https://github.com/sourcebot-dev/sourcebot/issues/new/choose) and we'll
get back to you as soon as we can." with a second-person, present-tense, short
version (e.g., "Have a question that's not answered here? Submit an issue on
GitHub and get a response as soon as possible.") so the message addresses the
reader directly and uses present tense; update the line in
docs/docs/configuration/auth/faq.mdx accordingly.
🪄 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: 0c89300e-c17a-49d9-acde-4d7c5b8e0d6d

📥 Commits

Reviewing files that changed from the base of the PR and between 937d04b and 79e03ee.

📒 Files selected for processing (1)
  • docs/docs/configuration/auth/faq.mdx

<Accordion title="How does Sourcebot implement authentication?">
Sourcebot uses [Auth.js](https://authjs.dev/) as its underlying authentication framework. Auth.js provides authentication providers
(credientials, Google, GitHub, etc) and an interface to enable user registration and log in. Internally, Auth.js uses JWT to provide
(credentials, Google, GitHub, etc) and an interface to enable user registration and log in. Internally, Auth.js uses JWT to provide
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.

⚠️ Potential issue | 🟡 Minor

Wrap technical values in inline code in this sentence.

Please format provider names as inline code to match docs style.

Suggested edit
-    (credentials, Google, GitHub, etc) and an interface to enable user registration and log in. Internally, Auth.js uses JWT to provide
+    (`credentials`, `Google`, `GitHub`, etc) and an interface to enable user registration and log in. Internally, Auth.js uses `JWT` to provide

As per coding guidelines, "Use bold for UI elements and inline code for technical values".

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
(credentials, Google, GitHub, etc) and an interface to enable user registration and log in. Internally, Auth.js uses JWT to provide
(`credentials`, `Google`, `GitHub`, etc) and an interface to enable user registration and log in. Internally, Auth.js uses `JWT` to provide
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/docs/configuration/auth/faq.mdx` at line 39, Update the sentence
containing "(credentials, Google, GitHub, etc) and an interface to enable user
registration and log in. Internally, Auth.js uses JWT to provide" by wrapping
the technical provider names and values in inline code formatting (e.g.,
`credentials`, `Google`, `GitHub`, `JWT`) so they follow the docs style; keep
the surrounding punctuation and wording unchanged and ensure only the
provider/technical tokens are converted to inline code.

</AccordionGroup>

Have a question that's not answered here? Submit an issue on [GitHub](https://github.com/sourcebot-dev/sourcebot/issues/new/choose) and we'll get back to you as soon as we can. No newline at end of file
Have a question that's not answered here? Submit an issue on [GitHub](https://github.com/sourcebot-dev/sourcebot/issues/new/choose) and we'll get back to you as soon as we can.
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.

⚠️ Potential issue | 🟡 Minor

Use second person and present tense for the closing CTA.

This line switches to first person and future tense. Please rewrite in second person/present tense.

Suggested edit
-Have a question that's not answered here? Submit an issue on [GitHub](https://github.com/sourcebot-dev/sourcebot/issues/new/choose) and we'll get back to you as soon as we can.
+If your question is not answered here, submit an issue on [GitHub](https://github.com/sourcebot-dev/sourcebot/issues/new/choose) to get help.

As per coding guidelines, "Write in second person and present tense. Keep sentences short."

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Have a question that's not answered here? Submit an issue on [GitHub](https://github.com/sourcebot-dev/sourcebot/issues/new/choose) and we'll get back to you as soon as we can.
If your question is not answered here, submit an issue on [GitHub](https://github.com/sourcebot-dev/sourcebot/issues/new/choose) to get help.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/docs/configuration/auth/faq.mdx` at line 44, Replace the closing CTA
sentence "Have a question that's not answered here? Submit an issue on
[GitHub](https://github.com/sourcebot-dev/sourcebot/issues/new/choose) and we'll
get back to you as soon as we can." with a second-person, present-tense, short
version (e.g., "Have a question that's not answered here? Submit an issue on
GitHub and get a response as soon as possible.") so the message addresses the
reader directly and uses present tense; update the line in
docs/docs/configuration/auth/faq.mdx accordingly.

@msukkari msukkari merged commit 44e7e62 into sourcebot-dev:main Apr 8, 2026
1 check passed
@wschoot wschoot deleted the patch-1 branch April 8, 2026 19:40
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