docs(enterprise): reshoot the installer screenshots against today's UI - #12673
Merged
Conversation
The six images under /enterprise/ all landed in one commit on 2025-12-10 and none has been touched since. This replaces the two that are furthest from what the installer looks like now, and fixes the one paragraph the reshoot proved wrong. The installer was redesigned — lowercase wordmark, light ground, black buttons — and step 1 gained a GitHub Server URL field. The prose already described that field; only the screenshot predated it. Both shots are retina 2x, captured off the installer the on-premise image actually serves: the engine monorepo's installer directory, built the way its Dockerfile builds it and served the way the entrypoint serves it, a plain static server over the build output. Step 2 downloads mergify.env on its own as soon as the App is created. The page said "Download the generated mergify.env, then click Install", which reads as a manual step. It now says what the installer does, what the file is for, and which button to use when a browser blocks the download. Four screenshots are not here yet: the two GitHub pages in the creation flow, the installer's own step 2, and the webhook deliveries view on the troubleshooting page. GitHub rejects an App manifest whose hook URL is not reachable over the public Internet, so none of those states can be reached without a public HTTPS origin serving the installer. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014f8ta8pKiB2g5TnS6PLTBY Change-Id: I3ab9cba7a25e46f282c0f74d7a604a03e3b929cc
Contributor
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
There was a problem hiding this comment.
🟢 Approval recommended
The change is a small, localized docs correction that improves accuracy and does not introduce any apparent leak or broken formatting.
Pull request overview
Updates the Mergify Enterprise installation documentation to match the current installer behavior/UI, specifically clarifying the mergify.env download step after GitHub App creation.
Changes:
- Reworded the post–GitHub App approval paragraph to reflect that the installer auto-downloads
mergify.env. - Added guidance for browsers that block the automatic download, pointing to the installer’s download button.
- Clarified what
mergify.envis used for (engine credentials in normal mode).
File summaries
| File | Description |
|---|---|
| src/content/docs/enterprise/installation.mdx | Updates the GitHub App installation flow prose to match the installer’s current automatic mergify.env download behavior. |
Review details
- Files reviewed: 1/3 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
jd
marked this pull request as ready for review
September 4, 2026 05:59
sileht
approved these changes
Sep 4, 2026
AlexandreGaubert
approved these changes
Sep 4, 2026
Contributor
Merge Queue Status
This pull request spent 10 minutes 39 seconds in the queue, including 9 minutes 22 seconds running CI. Required conditions to merge
|
63 tasks
mergify
Bot
deleted the
devs/jd/jd/reshoot-enterprise-install/reshoot-installer-screenshots-against-today-s-ui--3ab9cba7
branch
September 4, 2026 09:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The six images under /enterprise/ all landed in one commit on 2025-12-10 and
none has been touched since. This replaces the two that are furthest from what
the installer looks like now, and fixes the one paragraph the reshoot proved
wrong.
The installer was redesigned — lowercase wordmark, light ground, black buttons —
and step 1 gained a GitHub Server URL field. The prose already described that
field; only the screenshot predated it. Both shots are retina 2x, captured off
the installer the on-premise image actually serves: the engine monorepo's
installer directory, built the way its Dockerfile builds it and served the way
the entrypoint serves it, a plain static server over the build output.
Step 2 downloads mergify.env on its own as soon as the App is created. The page
said "Download the generated mergify.env, then click Install", which reads as a
manual step. It now says what the installer does, what the file is for, and
which button to use when a browser blocks the download.
Four screenshots are not here yet: the two GitHub pages in the creation flow,
the installer's own step 2, and the webhook deliveries view on the
troubleshooting page. GitHub rejects an App manifest whose hook URL is not
reachable over the public Internet, so none of those states can be reached
without a public HTTPS origin serving the installer.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_014f8ta8pKiB2g5TnS6PLTBY