How do AI-generated doc PRs get into DraftView?

Connect the GitHub App to your organization once. After that, every documentation PR in a connected repo (public or private) lands automatically in a shared review queue with its own lifecycle state, so nothing gets pasted in by hand and nothing falls through. You can still load any individual public PR by URL when you just want to try it.

Do my reviewers need a GitHub account?

No. Reviewers join your organization by email with a magic link and start reviewing right away, with no GitHub account or password. A GitHub-linked teammate then pushes their feedback upstream under a real account, so every suggestion stays properly attributed. For one-off outside reviewers like legal counsel or localization, you can also share a password-protected external link.

How does DraftView know which PRs were written by AI?

DraftView reads signals from the PR itself: the author, branch name, description, and commit trailers. Detection is generator-agnostic, so it works whether the docs came from Claude Code, Copilot, Cursor, or an in-house pipeline, and it is held to a strict precision bar before a label ever drives a filter or a metric. The label flags a PR for human review. It never blocks or merges anything on its own.

What happens after a reviewer requests changes?

Their comments and edits sync to GitHub as native review threads and Suggested Changes, so GitHub stays the single source of truth. When the agent pushes a new commit, the addressed view shows the before and after of the exact region they commented on, so the reviewer can confirm the feedback was really handled, not just that a line moved.

Does DraftView replace GitHub, or lock us in?

Neither. GitHub still owns your content, your comments, and the merge button. DraftView sits on top as a review layer you can add or remove at any time, and it never auto-merges. The one thing we keep that GitHub does not produce is the human-oversight record.

Can DraftView prove a human reviewed the AI's work?

Yes. Every sign-off writes an append-only record of who reviewed, what changed, how long they spent, and against which version. You can export a per-PR oversight audit, and the dashboard reports the share of AI doc PRs that received a substantive human review versus those rubber-stamped. That is the evidence a green checkmark cannot give you, framed around EU AI Act Article 14 human oversight.

Which documentation formats are supported?

We currently support standard Markdown, MDX and AsciiDoc. AsciiDoc renders correctly, however some features may not be fully functional. We are actively working on improving AsciiDoc support. If you have specific format needs, please contact us to discuss how we can accommodate your workflow.

We use X platform for documentation. Can I still use DraftView?

We support Docusaurus, Mintlify, GitBook, Hugo, MkDocs, and any other platform that uses a GitHub-based workflow. As long as your files are in a GitHub repository, we can render the preview.

We use GitLab/Bitbucket. Can we still use your visual review engine?

Not yet. DraftView currently only supports GitHub. We are building integrations for GitLab and Bitbucket next. Contact us to request priority for your platform.

Yes, all data is encrypted at rest and in transit. We follow industry best practices for security and compliance, including SOC2 readiness. Your documentation, review sessions, and the human-oversight record are protected with enterprise-grade security measures.

Is there a free tier or trial available?

Yes — DraftView is free forever for individuals and small teams. Reviewing PRs (public or private) is unlimited, and the free plan includes a review queue for 2 repos with 2 active reviewers per month. Connecting your GitHub organization starts a 14-day free trial of the Team plan (unlimited repos and reviewers, no credit card); when it ends you simply drop back to the free plan — nothing pauses. Team is $29/month per organization with 5 active reviewers included.

ProductJuly 7, 20266 min read

Edit Any GitLab File and Open a Merge Request in Your Browser

You can now edit Markdown, MDX, and AsciiDoc files from public GitLab repositories directly in your browser. DraftView handles the fork, commit, and merge request generation for you. No local setup required.

Documentation lives in your Git repositories, but editing it in the browser should not require a local development environment. Today, we are bringing our in-browser editor to GitLab. You can now open any Markdown, MDX, or AsciiDoc file from a public GitLab repository, edit the prose or code, and submit a merge request from your own GitLab account.

This extension expands on our GitHub integration. Whether you use GitHub or GitLab, you can now fix typos, update guides, and write documentation from any device with a browser.

The pain of web-based doc edits

Editing documentation in Git repositories usually requires a compromise. You can clone the repository, run a local terminal, and maintain a local copy. Alternatively, you can use a web IDE, which often lacks rich live previews for complex document formats.

For a quick change (like fixing a typo or updating a command), setting up a local editor is too much work. If you are editing an AsciiDoc file, you also need to manage include:: directives that pull text from other files. Finding those files manually in a repository structure is time-consuming.

DraftView removes this friction. You paste the GitLab file URL, and the editor opens the document. You make your changes, and DraftView automatically generates the merge request.

How to edit a GitLab file in one click

To edit a file, copy its URL from GitLab. The editor accepts standard GitLab file URLs, including links from nested subgroups, different branches, and tags.

Prepend the DraftView edit URL to the GitLab link:

https://www.draftview.app/edit?url=https://gitlab.com/YOUR_GROUP/YOUR_PROJECT/-/blob/main/docs/index.md

You can also paste the URL directly into the DraftView Editor.

The file loads instantly. You do not need to sign in to read or edit. The application only requests authorization when you click the submit button.

Visual and source editing modes

DraftView provides two editing modes so that you can choose the right tool for the job:

Visual mode: This mode works like a word processor. You edit the rendered version of your document. You see headings, lists, tables, and formatting exactly as they will look on the final page. This view is ideal for subject matter experts, product managers, and reviewers who do not want to interact with raw syntax.
Source mode: This mode provides a code editor with syntax highlighting, line numbers, and find-and-replace controls. You can use this mode for structural changes, such as configuring tables or editing custom components.

You can switch between the two modes at any time without losing your changes.

If you edit an AsciiDoc file, DraftView resolves all include:: directives automatically. It fetches the referenced files from your GitLab repository and lists them in a sidebar. You can edit the main file and the includes in the same editing session.

Submit merge requests directly from your account

When you submit your changes, DraftView uses GitLab OAuth to complete the process.

If you do not have write access to the repository, DraftView forks the project to your GitLab namespace, commits your changes to a new branch, and opens a merge request to the upstream project. The commit and the merge request appear under your GitLab username. Maintainers can review and merge your changes using their standard GitLab workflow.

Sign in with GitLab

We added GitLab as a first-class authentication provider. If you do not have a GitHub account, you can sign in directly with GitLab or request a magic link for your email inbox.

Free for public repositories

The browser editor is free to use for public repositories. You can edit files and submit merge requests without signing up for a paid plan.

Edit your first GitLab doc in seconds.

Paste any file URL from a GitLab repository, edit the content, and submit a merge request from your own account. Free for public repositories.

Try the editor

Free for public repositories. No credit card required.

Resources

Edit This Page Guide: Learn how to add an "Edit this page" button to your documentation site.
DraftView Editor: Paste a GitHub or GitLab URL to start editing immediately.
A Free Online AsciiDoc Editor That Opens Your Includes Too: Read our guide to editing AsciiDoc documents.