Mintlify
Previews for all pull requests #1724
Replies: 5 comments 1 reply
|
+1, preview deployments for forks would be greatly appreciated! |
|
Huge +1 to this. Our docs are open source, and when we get community contributions, there's no way to get a preview for a community contribution (or run CI through the mintlify validation process -- it has to be done manually, which is a slog). In an ideal world. I could have a list of allowlisted github account (or a team!) that are auto-previewed, and also have the authority to do a slash command in a comment, such as |
|
As a suggestion for what might be a good first step / low barrier to entry rather than doing the whole thing at once. Support |
|
This exists for custom CI triggers: https://www.mintlify.com/docs/api/preview/trigger but I suspect that it won't work with forks still, because they expect a branch name. I can't even do manual deploys of a branch from a fork. :/ 5 requests per minute is also nothing |
|
Support has confirmed it will work with forks. When triggering on a fork via the API I was able to start the deploy however it fails saying "Unable to find docs.json or mint.json" even though docs.json exists on the branch. |
|
+1 to the option to generate preview deployments regardless of PR branch. Often we do work off a staging branch off of main, and it'd be great to have those created automatically. |
Uh oh!
There was an error while loading. Please reload this page.
The standard workflow for open-source contribution on GitHub is to fork a repo, create a branch in the fork, and then make a pull request from the fork's branch to the upstream repository.
Mintlify currently only supports Previews for branches within the upstream repository, meaning Previews do not support the standard workflow for open-source contribution.
Please add support for generating Previews for all pull requests, regardless of where the PR branch lives.
All reactions