Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

jkim-dd
Copy link
Contributor

@jkim-dd jkim-dd commented Sep 12, 2025

What does this PR do? What is the motivation?

The Event Monitors doc page had a dead link in one of the info banners, to an old (presumably renamed) section header on the Configure Monitors page.

Merge instructions

Merge readiness:

  • Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

Additional notes

The Event Monitors doc page had a dead link in one of the info banners, to an old (presumably renamed) section header on the Configure Monitors page.
@jkim-dd jkim-dd requested a review from a team as a code owner September 12, 2025 00:09
Copy link
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@michaelcretzman
Copy link
Contributor

approved. let me know if you need help merging

@jkim-dd
Copy link
Contributor Author

jkim-dd commented Sep 12, 2025

Hi @michaelcretzman, thanks for the review! I'm not part of the docs team, so I am unfamiliar with the proper process of merging the changes - I've submitted PRs for doc changes in the past, but in prior cases the documentation team was able to review and finalize the PRs for me after they got approved.

I'd be happy to learn how to do so, in case I end up in this scenario again in the future.

Do I just need to hit the "Squash and merge" button within the workflow tile in this PR, in cases where there are no conflicts with base branch?

TYIA~

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