Fill gaps from assistant conversations: CI setup, multistep 4xx, on-prem - #500
Open
mintlify[bot] wants to merge 1 commit into
Open
Fill gaps from assistant conversations: CI setup, multistep 4xx, on-prem#500mintlify[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
Targeted updates to three pages based on recurring assistant conversation themes about CI credential setup, unexpected multistep check failures on expected non-2xx responses, and self-hosted/on-prem terminology.
Changes
integrations/ci-cd/gitlab/overview.mdx: added a Prerequisites section covering where to createCHECKLY_API_KEY(masked) andCHECKLY_ACCOUNT_IDas GitLab CI/CD variables and where to find the values.detect/synthetic-monitoring/multistep-checks/troubleshooting.mdx: added a section explaining that Playwright'srequestfixture does not throw on non-2xx responses, thattoBeOK()fails on expected 4xx statuses, and to assertresponse.status()explicitly.platform/private-locations/overview.mdx: clarified that Private Locations with the Checkly Agent are the option for running checks on-premises or in self-hosted infrastructure, so on-prem/self-hosted queries land on this page.