Skip to content

Conversation

v1v
Copy link
Member

@v1v v1v commented Sep 15, 2025

Motivation/summary

DRA should run for any branch and be clever enough to know what DRA branch to be used, that's ok for PRs, but it's not the case for feature branches that start with a different name than features/

Fixes

image

Checklist

For functional changes, consider:

  • Is it observable through the addition of either logging or metrics?
  • Is its use being published in telemetry to enable product improvement?
  • Have system tests been added to avoid regression?

How to test these changes

See https://buildkite.com/elastic/apm-server-package/builds/6196

Related issues

@v1v v1v requested a review from a team September 15, 2025 13:30
@v1v v1v self-assigned this Sep 15, 2025
@v1v v1v requested a review from a team as a code owner September 15, 2025 13:30
@v1v v1v added backport-8.19 Automated backport to the 8.19 branch backport-9.1 Automated backport to the 9.1 branch labels Sep 15, 2025
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@v1v v1v marked this pull request as draft September 15, 2025 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-8.19 Automated backport to the 8.19 branch backport-9.1 Automated backport to the 9.1 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant