Skip to content

docs: expand GitLab PAT scopes for Fern Editor setup#5127

Merged
Ryan-Amirthan merged 1 commit intomainfrom
devin/1776969765-fern-editor-gitlab-scopes
Apr 23, 2026
Merged

docs: expand GitLab PAT scopes for Fern Editor setup#5127
Ryan-Amirthan merged 1 commit intomainfrom
devin/1776969765-fern-editor-gitlab-scopes

Conversation

@Ryan-Amirthan
Copy link
Copy Markdown
Contributor

@Ryan-Amirthan Ryan-Amirthan commented Apr 23, 2026

Summary

Updates the GitLab personal access token scope list on the Fern Editor getting-started page to include all 5 required scopes: read_user, api, write_repository, read_repository, read_api (previously only listed api, read_repository, write_repository).

Per user request in Slack thread.

Affected page: https://buildwithfern.com/learn/docs/writing-content/fern-editor#getting-started

Review & Testing Checklist for Human

  • Confirm the 5 scopes listed are the correct set GitLab PATs need for Fern Editor (the 2 additions are read_user and read_api).
  • Verify the preview renders the scope list correctly.

Notes

Single-line edit to fern/products/docs/pages/component-library/writing-content/visual-editor.mdx.

Link to Devin session: https://app.devin.ai/sessions/1839a535396b4d19a54ff2885d8d2068
Requested by: @Ryan-Amirthan


Open in Devin Review

Co-Authored-By: ryanstep <ryanstep@umich.edu>
@Ryan-Amirthan Ryan-Amirthan requested a review from devalog as a code owner April 23, 2026 18:43
GitLab requires manual setup:

1. [Create a personal access token](https://gitlab.com/-/user_settings/personal_access_tokens) in GitLab with the following scopes: `api`, `read_repository`, `write_repository`. Set the expiration date far into the future to avoid disrupting your Editor experience — you can revoke the token at any time.
1. [Create a personal access token](https://gitlab.com/-/user_settings/personal_access_tokens) in GitLab with the following scopes: `read_user`, `api`, `write_repository`, `read_repository`, `read_api`. Set the expiration date far into the future to avoid disrupting your Editor experience — you can revoke the token at any time.
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.

⚠️ [vale] reported by reviewdog 🐶
[FernStyles.Current] Avoid time-relative terms like 'future' that become outdated

@github-actions
Copy link
Copy Markdown
Contributor

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

Open in Devin Review

@devin-ai-integration
Copy link
Copy Markdown
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@Ryan-Amirthan Ryan-Amirthan merged commit da86a1f into main Apr 23, 2026
4 checks passed
@Ryan-Amirthan Ryan-Amirthan deleted the devin/1776969765-fern-editor-gitlab-scopes branch April 23, 2026 19:58
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