Add faq #178
Add faq #178
Conversation
WalkthroughThe pull request updates the Changes
Possibly related PRs
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
docs/faq.md (3)
84-88: Consider adding email verification detailsThe instructions are clear, but it would be helpful to mention if there's an email verification step or when the changes take effect.
Consider adding:
To add or update your billing email, navigate to the Subscription page and select Manage Subscription > **Billing Address**. Enter your email address in the -Email field and click Update to save your changes. +Email field and click Update to save your changes. You will receive a verification +email at the new address to confirm the change.
161-165: Add references to GitLab documentationConsider adding links to GitLab's official documentation about permission levels and group management for both Cloud and Self-Hosted instances.
If you cannot view repositories in the CodeRabbit UI, please ensure that you are added as a Developer in the primary group for GitLab Cloud or in the first -level group for Self-Hosted GitLab. +level group for Self-Hosted GitLab. For more information, see +[GitLab's permission documentation](https://docs.gitlab.com/ee/user/permissions.html).
167-171: Add troubleshooting steps for persistent issuesConsider adding additional troubleshooting steps for cases where users have the correct permissions but still experience issues.
If you're having trouble enabling the GitLab Repositories toggle, confirm that you have Maintainer access in the primary group for GitLab Cloud or in the first -level group for Self-Hosted GitLab. +level group for Self-Hosted GitLab. + +If you still experience issues after confirming your permissions: +1. Try logging out and back in to refresh your session +2. Clear your browser cache +3. Contact support if the issue persists
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/faq.md(2 hunks)
🔇 Additional comments (1)
docs/faq.md (1)
Line range hint 84-171: LGTM! Document structure and formatting are well-maintained
The new FAQ entries are well-organized, properly formatted, and placed in appropriate sections. The content maintains consistency with the existing document structure.
No description provided.