Skip to content

Conversation

v1v
Copy link
Member

@v1v v1v commented Sep 15, 2025

Motivation/summary

Use the BK PR Bot to run the apm-server-package on PRs too.

This should help with detecting breaking changes in the Unified Release before merging when using forked PRs. The only way to test that currently is by using a feature branch in the upstream.

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

Related issues

@v1v v1v requested review from a team September 15, 2025 08:59
@v1v v1v self-assigned this Sep 15, 2025
@v1v v1v requested a review from a team as a code owner September 15, 2025 08:59
@v1v v1v added the backport-skip Skip notification from the automated backport with mergify label 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!)

Copy link
Contributor

@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@carsonip carsonip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rubber stamping

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-skip Skip notification from the automated backport with mergify

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants