Add Datadog Synthetic tests workflow

[kerrrang9214-tech]

This workflow triggers Datadog Synthetic tests on push and pull request events to the main branch.

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

This pull request contains code changes, so we will not generate a table of review links.

🤖 This comment is automatically generated.

[github-actions]

👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:

• .github/workflows/datadog-synthetics.yml

You'll need to revert all of the files you changed that match that list using GitHub Desktop or git checkout origin/main <file name>. Once you get those files reverted, we can continue with the review process.

The complete list of files we can't accept are:

• .devcontainer/**
• .github/**
• data/reusables/rai/**
• Dockerfile*
• src/**
• package*.json
• content/actions/how-tos/security-for-github-actions/security-hardening-your-deployments/**

We also can't accept contributions to files in the content directory with frontmatter contentType: rai.

[Copilot]

Pull request overview

Adds a new GitHub Actions workflow to run Datadog Synthetic tests when changes are pushed to main or when pull requests target main.

Changes:

• Introduces .github/workflows/datadog-synthetics.yml to run Datadog Synthetics via DataDog/synthetics-ci-github-action.
• Configures triggers for push and pull_request events on the main branch.
• Uses repository secrets (DD_API_KEY, DD_APP_KEY) and a tag-based search query (tag:e2e-tests) to select tests.

[github-actions]

👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:

• .github/workflows/datadog-synthetics.yml

You'll need to revert all of the files you changed that match that list using GitHub Desktop or git checkout origin/main <file name>. Once you get those files reverted, we can continue with the review process.

The complete list of files we can't accept are:

• .devcontainer/**
• .github/**
• data/reusables/rai/**
• Dockerfile*
• src/**
• package*.json
• content/actions/how-tos/security-for-github-actions/security-hardening-your-deployments/**

We also can't accept contributions to files in the content directory with frontmatter contentType: rai.

[kerrrang9214-tech]

[240623]

This workflow triggers Datadog Synthetic tests on push and pull request events to the main branch.

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[biometricdiwan-web]

Closed it make him error permanently doc file 44197

…

On Thu, 14 May 2026 at 02:05, github-actions[bot] ***@***.***> wrote: Closed #44196 <#44196>. — Reply to this email directly, view it on GitHub <#44196 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CDJRYJQLOBJUV5SFAXKJFRL42TWUDAVCNFSM6AAAAACYWYTTQKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRVGUYDENRYGQ3TOOI> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>