-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: refactored integration guides images SEO and accessibility #129
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||
---|---|---|---|---|---|---|---|---|
|
@@ -27,15 +27,15 @@ To interact with the GitLab API, a **Personal Access Token** is required. This t | |||||||
|
||||||||
Upon first login to the application (immediately after the onboarding screen), you will need to choose based on your organization's requirements. | ||||||||
|
||||||||
![gitlab user modal choice](/img/integrations/gitlab_user_choice.png) | ||||||||
![GitLab repository access configuration modal showing how to choose between default CodeRabbit user or organization user token](/img/integrations/gitlab_user_choice.png) | ||||||||
|
||||||||
**We recommend using the default CodeRabbit user** for most organizations, as it is pre-configured. However, we understand that some organizations may prefer more control over the user or have restrictions regarding user inclusion within their organization. | ||||||||
|
||||||||
### Personal Access Tokens | ||||||||
|
||||||||
If your organization opts to use another user within the organization, you can do so by [generating a personal access token](#generating-a-personal-access-token). | ||||||||
|
||||||||
![gitlab organization user modal choice](/img/integrations/gitlab_organization_user.png) | ||||||||
![GitLab integration configuration modal showing personal access token input field and organization user setup with detailed instructions for token integration](/img/integrations/gitlab_organization_user.png) | ||||||||
|
||||||||
#### Recommendations | ||||||||
|
||||||||
|
@@ -67,4 +67,4 @@ GitLab provides an option to generate a personal access token for a new user. Fo | |||||||
9. Click "Create Personal Access Token." | ||||||||
10. Note down the token as it will only be displayed once. | ||||||||
|
||||||||
![Untitled](/img/integrations/admin-access-token.png) | ||||||||
![GitLab personal access token configuration page showing token name input, expiration date selector, and API permission scopes including read/write access options](/img/integrations/gitlab-personal-access-token-scopes-setup.png) | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Add newline at end of file. Add a newline character at the end of the file to follow Markdown best practices and improve compatibility. ![GitLab personal access token configuration page showing token name input, expiration date selector, and API permission scopes including read/write access options](/img/integrations/gitlab-personal-access-token-scopes-setup.png)
+ 📝 Committable suggestion
Suggested change
🧰 Tools🪛 Markdownlint70-70: null (MD047, single-trailing-newline) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix ordered list numbering sequence.
The ordered list numbers are not sequential (jumps from 1 to 3 to 4 to 5), which can impact accessibility and screen reader functionality.
Apply this fix:
🧰 Tools
🪛 Markdownlint
33-33: Expected: 1; Actual: 3; Style: 1/2/3
Ordered list item prefix
(MD029, ol-prefix)
34-34: Expected: 2; Actual: 4; Style: 1/2/3
Ordered list item prefix
(MD029, ol-prefix)
36-36: Expected: 3; Actual: 5; Style: 1/2/3
Ordered list item prefix
(MD029, ol-prefix)