Skip to content

Conversation

@aali309
Copy link
Contributor

@aali309 aali309 commented Mar 21, 2025

This PR is a cherry-pick from #21771

Original PR Details

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

@aali309 aali309 marked this pull request as ready for review March 24, 2025 21:08
@aali309 aali309 requested a review from a team as a code owner March 24, 2025 21:08
@aali309
Copy link
Contributor Author

aali309 commented Mar 24, 2025

@anandf, @svghadi , I need help resolving this please. The additional files changed are as a result of ci linter failures

@aali309 aali309 closed this Jun 4, 2025
@aali309 aali309 deleted the cherry-pick-release-2.12 branch June 4, 2025 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants