Skip to content

Conversation

@pranav-new-relic
Copy link
Member

TBD

@github-actions
Copy link

Hi @pranav-new-relic 👋

Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days.

Please ensure the propsed changes look good by building it first in your local environment. Refer to this contribution guide to get the site up and running in your local.

If you really require a preview url, reach out to one of the writers and they will generate one for you.

@pranav-new-relic
Copy link
Member Author

Hey @copilot, here's what the results of the workflow verify mdx files state

Failed MDX file count: 6
[
'/home/runner/work/docs-website/docs-website/src/i18n/content/es/docs/alerts/get-notified/notification-integrations.mdx',
'/home/runner/work/docs-website/docs-website/src/i18n/content/fr/docs/alerts/get-notified/notification-integrations.mdx',
'/home/runner/work/docs-website/docs-website/src/i18n/content/jp/docs/alerts/get-notified/notification-integrations.mdx',
'/home/runner/work/docs-website/docs-website/src/i18n/content/kr/docs/alerts/get-notified/notification-integrations.mdx',
'/home/runner/work/docs-website/docs-website/src/i18n/content/pt/docs/alerts/get-notified/notification-integrations.mdx',
'/home/runner/work/docs-website/docs-website/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx'
]
❌ Found 6 MDX errors
Error 1: MDX error: /home/runner/work/docs-website/docs-website/src/i18n/content/es/docs/alerts/get-notified/notification-integrations.mdx
Unexpected end of file in element, expected a corresponding MDX closing tag for <Callout> (182:5-182:34)
line: 183
column: 32
Error 2: MDX error: /home/runner/work/docs-website/docs-website/src/i18n/content/fr/docs/alerts/get-notified/notification-integrations.mdx
Unexpected end of file in element, expected a corresponding MDX closing tag for <Callout> (182:5-182:34)
line: 183
column: 39
Error 3: MDX error: /home/runner/work/docs-website/docs-website/src/i18n/content/jp/docs/alerts/get-notified/notification-integrations.mdx
Unexpected end of file in element, expected a corresponding MDX closing tag for <Callout> (182:5-182:34)
line: 183
column: 13
Error 4: MDX error: /home/runner/work/docs-website/docs-website/src/i18n/content/kr/docs/alerts/get-notified/notification-integrations.mdx
Unexpected end of file in element, expected a corresponding MDX closing tag for <Callout> (182:5-182:34)
line: 183
column: 14
Error 5: MDX error: /home/runner/work/docs-website/docs-website/src/i18n/content/pt/docs/alerts/get-notified/notification-integrations.mdx
Unexpected end of file in element, expected a corresponding MDX closing tag for <Callout> (182:5-182:34)
line: 183
column: 32
Error 6: MDX error: /home/runner/work/docs-website/docs-website/src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx
Unexpected end of file in element, expected a corresponding MDX closing tag for <Callout> (46:5-46:34)
line: 46
column: 34
error Command failed with exit code 1.

Based on the details of this error, it looks like there are changes needed to the listed files. On the basis of fixes which have been made in the past to similar files in response to the failing verify MDX workflow, can you edit these files accordingly to ensure the right changes are in place and the verify mdx files workflow succeeds?

Copy link

Copilot AI commented Nov 14, 2025

@pranav-new-relic I've opened a new pull request, #22208, to work on those changes. Once the pull request is ready, I'll request review from you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants