Update from support feedback: clarify Git integration network requirements - #7172
Open
mintlify[bot] wants to merge 5 commits into
Open
Update from support feedback: clarify Git integration network requirements#7172mintlify[bot] wants to merge 5 commits into
mintlify[bot] wants to merge 5 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
- Updated deploy/ghes.mdx - Updated deploy/gitlab-self-hosted.mdx Mintlify-Source: dashboard-editor
Resolves the nav conflicts with #7276 and narrows this PR to the substantive content changes. - Correct the static-IP claims. 54.242.90.151 is the platform's egress IP (API calls, check runs, deployment statuses). Agent sandboxes use dynamic IPs unless support enables the static-egress-proxy flag for a deployment, so clone/push is no longer attributed to the static IP. This removes the contradiction with help-center/agent-blocked-by-git-provider-ip-allow-list (#7276) and cross-links it from all three pages. - Revert the Steps reindentation in deploy/ghes.mdx, leaving only the network requirements rewrite. - Revert the hand-edited es/fr/zh files and nav entries; translations run automatically after merge. - Add a language tag to the IP code block and fix Vale term errors. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
2 participants
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.
Summary
Support threads from enterprise customers showed the GHES firewall docs conflate inbound and outbound traffic, and the self-hosted GitLab page has no egress-IP guidance. This PR rewrites the GHES network requirements to state the direction of each connection (outbound to
leaves.mintlify.comby hostname; inbound from static egress IP54.242.90.151), adds a matching network requirements section to the self-hosted GitLab page, and adds a help center article answering "What IPs does Mintlify connect to my Git provider from?"Changes
deploy/ghesnetwork requirements with explicit outbound/inbound sectionsdeploy/gitlab-self-hostedhelp-center/ip-addresses-for-git-provider-allowlistsand registered it in the naves/,fr/,zh/and updatedes.json,fr.json,zh.jsonnavigationSupport context
Note
Low Risk
Documentation-only changes to deployment and help-center pages; no application or security logic is modified.
Overview
Clarifies bidirectional firewall requirements for enterprise Git integrations so customers do not mix up webhook egress with Mintlify ingress.
The GHES network section is rewritten into separate outbound (webhooks to
leaves.mintlify.comby hostname + DNS) and inbound (API from static egress54.242.90.151) guidance, with a note that Agent clone/push may use dynamic IPs and links to the existing allowlist troubleshooting article.Self-hosted GitLab OAuth gets a matching Network requirements block (inbound from
54.242.90.151, outbound webhooks toapp.mintlify.comby hostname) plus the same Agent/automation caveat.A new help center article documents when to allowlist
54.242.90.151, how Agent traffic differs, and that Mintlify inbound webhook targets are hostname-based without published static IPs; it is registered indocs.jsonnavigation.Reviewed by Cursor Bugbot for commit f7a9007. Bugbot is set up for automated code reviews on this repo. Configure here.