Skip to content

Conversation

@v1v
Copy link
Member

@v1v v1v commented Oct 23, 2025

Motivation/summary

Avoid issues when running the FF and use a ref branch other than main.

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

In the CI

If a different branch and no force

Screenshot 2025-10-23 at 14 12 27 Screenshot 2025-10-23 at 14 20 02

If a different branch and force

Screenshot 2025-10-23 at 14 20 25 Screenshot 2025-10-23 at 14 20 50

Related issues

@v1v v1v self-assigned this Oct 23, 2025
@v1v v1v requested review from a team as code owners October 23, 2025 12:22
@v1v v1v added backport-skip Skip notification from the automated backport with mergify backport-8.19 Automated backport to the 8.19 branch backport-9.2 Automated backport to the 9.2 branch and removed backport-skip Skip notification from the automated backport with mergify labels Oct 23, 2025
@github-actions
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

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.2 Automated backport to the 9.2 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants