Skip to content

Conversation

@bksagar
Copy link
Contributor

@bksagar bksagar commented Sep 9, 2025

Description

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

@bksagar bksagar requested a review from nupurg-ibm as a code owner September 9, 2025 12:57
@bksagar
Copy link
Contributor Author

bksagar commented Sep 9, 2025

/run pipeline

nupurg-ibm
nupurg-ibm previously approved these changes Sep 9, 2025
@nupurg-ibm
Copy link
Collaborator

/run pipeline

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.

3 participants