fixing dependabot PR CI

[bm1549]

Description

Skips Datadog test-report and coverage uploads when DD_CI_VIS_API_KEY is unavailable. Builds and tests still run, and JUnit uploads still run after a test failure when the key exists. The key itself is scoped to the upload steps.

Motivation

GitHub does not expose Actions secrets to Dependabot or fork pull requests, and reusable workflows may be called without inherited secrets. These runs were failing after successful builds and tests because upload steps ran with an empty key.

Additional Notes

Validated with actionlint and credential-condition checks.

Jira ticket: N/A

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-07-30 18:07:17

Comparing candidate commit 48ae01e in PR branch brian.marks/fix-dependabot-pr-ci with baseline commit 091059d in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 8 metrics, 0 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

[datadog-datadog-prod-us1]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 91.75% (+0.00%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 48ae01e | Docs | Datadog PR Page | Give us feedback!}

[zacharycmontoya]

LGTM, thanks for looking into this!