Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
171 changes: 148 additions & 23 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,43 +1,168 @@
# Mergify Docs
# Mergify Documentation

This repository contains the code responsible for building the Mergify Docs
site.
The source code for [docs.mergify.com](https://docs.mergify.com) — the official documentation for Mergify, the merge queue and CI optimization platform.

## Developing locally
Built with [Astro](https://astro.build/) and MDX.

Run a local server to see your changes.
## Prerequisites

1. Install NPM dependencies:
You need **Node.js 24** installed on your machine. If you don't have it yet:

- **macOS** (using [Homebrew](https://brew.sh)):
```sh
brew install node@24
```
- **Any platform** (using [nvm](https://github.com/nvm-sh/nvm)):
```sh
nvm install 24
nvm use 24
```
- **Or download directly** from [nodejs.org](https://nodejs.org/)

You can verify your Node version with:

```sh
node --version
# Should output v24.x.x
```

> **Note:** The required version is specified in the `.node-version` file at the root of this repository. Tools like `nvm`, `fnm`, and `mise` can read this file automatically.

## Getting Started

1. **Clone the repository:**

```sh
git clone https://github.com/Mergify/mergify-docs.git
cd mergify-docs
```

2. **Install dependencies:**

```sh
npm i
npm install
```

2. Start the local development environment:
This downloads all the packages the project needs. It may take a minute the first time.

3. **Start the development server:**

```sh
npm start
```

Note that in dev mode like this, a page is built only when accessing it from the browser.
So it may take a few seconds when navigating through pages.
Open [http://localhost:4321](http://localhost:4321) in your browser to see the site.

## Preview prod build
> Pages are built on-demand in dev mode, so the first visit to each page may take a few seconds.

You can build docs and run a preview close to how it's done in production
## Common Commands

1. Build the docs
| Command | What it does |
| -------------------- | ----------------------------------------------------- |
| `npm start` | Start the local development server |
| `npm run build` | Build the full site for production (with type checks) |
| `npm run preview` | Preview the production build locally |
| `npm run check` | Run all linting and type checks |
| `npm run format` | Auto-format code with Biome |
| `npm run format:check` | Check formatting without changing files |
| `npm test` | Run unit tests with Vitest |

```sh
npm run build
```
## Project Structure

2. Run the preview
```
src/
├── content/
│ ├── docs/ # Documentation pages (MDX files) — this is where most edits happen
│ └── changelog/ # Changelog entries
├── components/ # Astro and React UI components
├── layouts/ # Page layout templates
└── util/ # Utility functions
integrations/ # Custom Astro integrations
plugins/ # Custom Remark/Rehype plugins
public/ # Static assets (images, fonts, etc.)
```

```sh
npm run preview
```
### Documentation content

All documentation lives in `src/content/docs/` as `.mdx` files. The main sections are:

- `configuration/` — Mergify configuration reference
- `merge-queue/` — Merge queue features and setup
- `commands/` — GitHub comment commands
- `ci-insights/` — CI analytics and optimization
- `merge-protections/` — Branch protection rules
- `integrations/` — Third-party integrations
- `enterprise/` — Enterprise features

## Editing Documentation

Each `.mdx` file starts with frontmatter — metadata between `---` fences:

```mdx
---
title: My Page Title
description: A short description of the page.
---

Your content here, written in Markdown.
```

Both `title` and `description` are **required**.

### Callout boxes

Use directive syntax for callout boxes:

```mdx
:::note
Important information here.
:::

:::tip
Helpful suggestion.
:::

:::caution
Be careful about this.
:::
```

### Images

Place images in `src/content/docs/images/` and use relative imports in your MDX files.

## Before You Commit

Always run the checks before pushing your changes:

```sh
npm run check
```

This runs TypeScript type checking, ESLint, and Biome formatting checks all at once. Fix any errors before committing.

You can also do a full production build to catch issues that only appear when building all pages:

```sh
npm run build
```

## Production Build Preview

To see exactly what the site will look like in production:

```sh
npm run build && npm run preview
```

> The build compiles every page, so you may see errors here that don't appear in dev mode (where pages are built one at a time).

## Tech Stack

Note that during the build, you can encounter some errors that you won't see in local dev.
This is because you're building every single page, in opposite of a local dev server that builds
pages when you visit them.
- **Framework:** [Astro 5](https://astro.build/) with MDX
- **UI:** React 19, Vue (for select components)
- **Language:** TypeScript (strict mode)
- **Formatter:** [Biome](https://biomejs.dev/)
- **Linter:** ESLint 9
- **Tests:** Vitest
- **Deployment:** Cloudflare Pages
Loading