Skip to content

Conversation

dalextorres
Copy link
Contributor

What does this PR do? What is the motivation?

We're adding documentation so Supabase users have an easy guide to install the Database Monitoring product on their instances.

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

@dalextorres dalextorres requested review from a team as code owners October 23, 2025 16:49
@github-actions
Copy link
Contributor

github-actions bot commented Oct 23, 2025

@estherk15
Copy link
Contributor

Thanks for opening this PR! Created an editorial review: https://datadoghq.atlassian.net/browse/DOCS-12411

@estherk15 estherk15 added the editorial review Waiting on a more in-depth review label Oct 23, 2025
@github-actions github-actions bot added the Architecture Everything related to the Doc backend label Oct 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Architecture Everything related to the Doc backend editorial review Waiting on a more in-depth review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants