Skip to content
This repository was archived by the owner on Jan 8, 2025. It is now read-only.

Add an RFD for a Mintlify migration workflow #444

Closed
wants to merge 1 commit into from

Conversation

ptgott
Copy link
Contributor

@ptgott ptgott commented Mar 14, 2024

Adding the design doc within the docs repo allows it to live beside the most substantial portion of the code that is based on it for easier discoverability.

Adding the design doc within the `docs` repo allows it to live beside
the most substantial portion of the code that is based on it for easier
discoverability.
@ptgott ptgott requested a review from wadells March 14, 2024 19:47
@ptgott ptgott requested a review from avatus as a code owner March 14, 2024 19:47
Copy link

vercel bot commented Mar 14, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 14, 2024 7:55pm

Copy link

@wadells wadells left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sasha has requested this is put on hold while we assess the impact of https://mintlify.com/blog/incident-march-13

documentation PR we merge to gravitational/teleport. This document outlines a
high-level plan for managing the dual deployment.

## How Mintlify works
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a section here about the Mintlify Github app, and how it should be configured.

Particularly, the Mintlify GitHub App will need to be installed on the teleport org, but we want to make sure:

  • it doesn't have any org scopes
  • it is limited to the "read content" repo scope
  • the only allowed repo is docs

@ptgott ptgott closed this Apr 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants