galley.
Live demoDemo Get Galley

Clearer reviews for GitHub & GitLab

Understand changes.Review in peace.

Help your team see what changed and how it fits together. Galley makes documents and code easier to read, shows edits in context, and keeps review comments beside the text they discuss.

Add to Chrome Try live demo

Free & open source No account Chrome, Edge, Brave, Arc

Installation guide
0042-limits.md 2 of 5

RFC 0042 · Changes in context

Rate limits,
revisited.

2 min read 2 edits1 conversation

Each client may send 10 100 requests a minute to support larger batch uploads.

src/limits.ts

12 export const limit = { 13− perMinute: 10, 13+ perMinute: 100,
D Dana on this paragraph

Does this cover batch uploads?

L

Lee Yes. I’ll add an example to make that clearer.

Viewed02 / 05

docs/rfcs/0042-limits.md

@@ -11,6 +11,7 @@ -## Limits +## Rate limits, revisited -Each client may send **10** requests a -minute to support larger batch uploads. +Each client may send **100** requests a +minute to support larger batch uploads.

src/limits.ts

@@ -12,3 +12,3 @@ export const limit = { - perMinute: 10, + perMinute: 100,

docs/review-modes.md

@@ -3,5 +3,5 @@ | Mode | Shows | - |---------|----------------------| + | ------- | -------------------- | - - [ ] Render tables + - [x] Render tables The same document and code changes, shown as a diff.

Sample review. Switch views to compare.

Try the live demo

Works where your
team already reviews.

GitHub
GitLab
Self-hosted GitHub & GitLab.
Enable each site in the extension.

Why Galley exists

See the edits.
Follow the idea.

A useful review starts with understanding the change.

A pull request can span a proposal, a README and several source files. To review it well, your team needs to follow the explanation, inspect the edits and connect the discussion to the right text.

Galley brings those parts into one readable view. Documents keep their headings and tables. Code keeps its line numbers. Changes stay beside the context that helps you understand them.

More context for every reviewer. Ask a question beside the change, reply in the same thread, and keep the discussion on GitHub or GitLab.

  1. 01 · Open the review

    Press Read on your GitHub pull request or GitLab merge request.

  2. 02 · Read with context

    Follow the document as an article. Turn on Code files to include source changes.

  3. 03 · Inspect the edits

    See changed words in their sentences and changed code with line numbers. Expand unchanged sections when you need more context.

  4. 04 · Discuss the change

    Add comments and replies beside the relevant text. Your team sees them in the original review.

  5. 05 · Keep your place

    Mark files as viewed as you go, then return to GitHub or GitLab to submit your review.

The same changes, easier to follow

From the diff
to the full picture.

Drag the divider to compare the demo’s diff view with the Galley reader. The files and comments are the same; Galley makes the text, edits and discussion easier to follow together.

The merge request in Galley: a typeset document with edits marked in place and a comment thread beside its paragraph.
The same merge request as a diff: one monospace column of red and green lines, with a Read button in the corner.
The diff Galley

How Galley helps

Context for the change.
Space for the discussion.

Read the proposal, inspect the code and discuss the details in one view. These features help your team understand what changed before deciding what to do next.

  1. 01

    Make the content readable.

    Read documents with headings, tables, task lists and diagrams. Include code files with syntax colours, line numbers and long lines that wrap to fit the screen.

    Follow the explanation and the implementation.

  2. 02

    See edits in context.

    Added words are highlighted and removed words struck through inside their sentences. Table edits appear in their cells, and changed link destinations are called out.

    Understand the detail and the surrounding idea.

  3. 03

    Focus on what changed.

    Re-wrapping a paragraph doesn’t mark it as a text change. Unchanged sections fold away; open them whenever you need the context.

    Your scrollbar gets a breather.

  4. 04

    Discuss it beside the text.

    Read threads beside the paragraph or code line they discuss. Select text to add a comment, reply in the thread, and keep your draft while you read on.

    Teammates can reply on GitHub or GitLab.

  5. 05

    Find your reading comfort.

    Choose from nineteen palettes, six typefaces, five text sizes and six layouts. Use light or dark mode, compact spacing and keyboard shortcuts.

    Adjust the view to suit your screen and your eyes.

  6. 06

    Keep your work on your code host.

    Files render in your browser and comments go to the original review. Galley has no server, account or analytics. External images load only when you choose.

    Works with your team’s existing review process.

See it in action

One review.
A clearer view.

Explore real screenshots from the Galley demo: edits, comments, code, tables and diagrams. Open the live demo to try the reader yourself.

The Galley reader showing a rendered RFC with edits marked in the text, a contents column and a comment thread in the margin.
Read the document with edits in context, a contents list on the left and review comments on the right.Try the live demo

At a glance

Easy to start.
Yours to adjust.

0
Galley accounts needed. Use your existing GitHub or GitLab access.
1
Read button. Opens changed documents and supported code files.
16
Reading palettes. Each available in light and dark.
6
Typeface choices. Find the text style that suits you.
5
Reader layouts. Choose space for text, code or comments.

Built for your team

Shared context.
Better conversations.

Give reviewers a clear view of the work so they can ask useful questions and explain their feedback. Galley keeps the files, edits and comments connected, while your team continues reviewing on GitHub or GitLab.

Explore the source code

Open source.

Free and GPL-licensed. The code, permissions and known limitations are open for you to inspect.

Private by default.

Rendering happens in your browser. No Galley server, no analytics, no telemetry. External images wait for your permission.

Your existing workflow.

Files come from your code host. Comments go back to the same review. Teammates don’t need Galley to join in.

Get the extension

Bring clarity
to your next review.

Add Galley to desktop Chrome, open a GitHub pull request or a GitLab merge request, and press Read.

Add to Chrome

Want to try it first? The demo works in your browser, including on a phone.

Try the live demo
Available in the Chrome Web Store

Start with three steps.

  1. 01

    Open Galley in the Chrome Web Store.

  2. 02

    Choose Add to Chrome, then confirm Add extension.

  3. 03

    Open a GitHub pull request or GitLab merge request and press Read.

No Galley account needed. Private GitHub repositories need a token; see the setup details below.

Do my teammates need Galley?

No. Comments and replies appear in the original GitHub or GitLab review. Teammates can read and respond there, whether or not they use Galley.

Can I review code as well as documents?

Yes. Markdown documents open as readable articles. Turn on Code files in Reading settings → Review to include supported source and configuration files, with syntax colours, wrapped lines and comments beside the code.

Does it work with private repositories?

Yes. GitLab uses your signed-in session. Private GitHub repositories need a fine-grained token, saved in the extension: read-only Contents and Pull requests to read, plus Pull requests write access to comment.

Self-hosted GitLab and GitHub Enterprise Server are enabled one domain at a time from the extension popup. Read the setup guide ↗

Where do my files and comments go?

Galley loads files from your GitHub or GitLab site and renders them in your browser. Comments go back to that review when you post. There is no Galley server or analytics. The demo keeps comments in your browser session and doesn’t post to either platform.

Read the full privacy policy →

Which browsers does it support?

Chrome, and Chromium browsers such as Edge, Brave and Arc, from the Chrome Web Store. A Firefox build comes with every GitHub release; the Firefox Add-ons listing isn’t published yet. Safari isn’t packaged.

How does it help my team review changes?

Galley puts readable content, edits and discussion in one view. Reviewers can follow the proposal, inspect a change in context and ask a question beside it. We haven’t measured review speed; the focus is helping people understand the work.

Can I approve a request from Galley?

You can read, comment, reply and mark files as viewed in Galley. Return to GitHub or GitLab to approve the request, request changes or resolve a thread.