Flaky Tests Management: document attempt-to-fix detection across batched commits

[TovRudyy]

What does this PR do?

Updates the Flaky Tests Management page to document an improvement to the attempt-to-fix remediation flow: Datadog now detects the unique test key (for example, DD_ABC123) in any commit included in the triggering push, not only the most recent commit.

Do not merge immediately

Motivation

Previously the key was reliably detected only in the commit that triggered the test run (typically the head commit). When commits were pushed together or squashed — or when a CI provider reported only the head commit — the key could be missed if it lived in an earlier commit of the push. The flow now triggers regardless of which commit in the push carries the key, and CI retries of the same push are not double-processed. No user configuration is required.

Scope

One-line content change in content/en/tests/flaky_management/_index.md, in the Confirm fixes for flaky tests section. User-facing wording only — no API or behavior contract changes.

Reference: SDCT-332

[drichards-87]

Left some minor feedback from Docs and approved the PR.

[drichards-87]

Suggested change

	1. When Datadog detects the test key, it automatically triggers the remediation flow for that test. The key does not need to be in the most recent commit, because Datadog also checks the recent commits leading up to it, so the flow still triggers when you push several commits together or when your CI provider reports only the most recent commit. The remediation flow:
	1. When Datadog detects the test key, it automatically triggers the remediation flow for that test. The key does not need to be in the most recent commit. Datadog also checks recent preceding commits, so the flow still triggers when you push several commits together or when your CI provider reports only the most recent commit. The remediation flow:

[drichards-87]

Suggested change

	After you include the test key (for example, `DD_ABC123`) in a commit, Datadog scans the commit that triggered the test run and up to the 10 most recent commits in its history. If the remediation flow does not start, check the following:
	After you include the test key (for example, `DD_ABC123`) in a commit, Datadog scans the commit that triggered the test run and up to the 10 most recent commits before it. If the remediation flow does not start, check the following:

[drichards-87]

Suggested change

	- **The key is in an older commit.** Only the 10 most recent commits in the triggering commit's history are scanned. If you push more than 10 commits at once, include the key in the triggering commit or within its 10 most recent commits.
	- **The fix was squash-merged.** A squash merge combines the original commits into a single commit, so Datadog reads only the squash commit's message; the individual pre-squash commits are no longer scanned. Most providers include the original commit messages in the squash commit, so a key in any of them is preserved. If your provider omits them, add the key to the squash commit message.
	- **The key does not match the expected format.** Use the exact key shown in the Flaky Tests Management UI (for example, `DD_ABC123`) in the commit title or message.
	- **The key is in an older commit.** Datadog scans only the triggering commit and the 10 most recent commits in its history. If you push more than 10 commits at once, include the key in the triggering commit or one of the 10 most recent commits.
	- **The fix was squash-merged.** A squash merge combines the original commits into a single commit, so Datadog reads only the squash commit's message; the individual pre-squash commits are no longer scanned. Most providers include the original commit messages in the squash commit, so a key in any of them is preserved. If your provider omits them, add the key to the squash commit message.
	- **The key does not match the expected format.** Use the exact key shown in the Flaky Tests Management UI (for example, `DD_ABC123`) in the commit title or message.

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/olek.rudyy/SDCT-332-ftm-attempt-to-fix-batched-commits/tests/flaky_management/

[github-actions]

⚠️ Possible site support note detected

The following files have a site-region shortcode at the top of the page that mentions a feature being "not available" or "not supported":

• content/en/tests/flaky_management/_index.md

Are you trying to document site support for a product? If so, the site-region shortcode is not the recommended approach. See the Documenting site support guide for the preferred method.