Fill gaps from assistant conversations: checkMatch arrays and env add - #466
Open
mintlify[bot] wants to merge 1 commit into
Open
Fill gaps from assistant conversations: checkMatch arrays and env add#466mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Close two documentation gaps surfaced by recurring assistant conversations: how to match multiple file globs with
checkMatch, and what to do whencheckly env addtargets a key that already exists.Changes
constructs/project.mdx: correctchecks.checkMatchtype fromstringtostring | string[]in both the properties table and the ResponseField, and add an inline example showing an array of globs.constructs/including-checks.mdx: note thatcheckMatchalso accepts an array of glob patterns, with an example matching multiple file extensions.cli/checkly-env.mdx: add a note undercheckly env addclarifying that it is for creating new variables only, pointing users tocheckly env updatefor existing keys and tocheckly env rm+add --secretfor converting a plain variable to a secret.Context
Assistant sessions repeatedly asked how to include multiple check file extensions and what happens when
env addis called for an existing key; the existing pages were ambiguous or silent on both points.