fix: pre-commit issues #272
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
/run pipeline |
ocofaigh
reviewed
Dec 9, 2025
ibm_catalog.json
Outdated
| { | ||
| "label": "Fully configurable", | ||
| "name": "fully-configurable", | ||
| "short_description": "Fully configurable Monitoring and Workload Protection agent deployment for OpenShift or Kubernetes clusters", |
Contributor
There was a problem hiding this comment.
Please use the "Ideal for ..." terminology we have been using in all other DAs
Updated the Fully configurable flavor short_description to follow the recommended format that begins with "Ideal for", making it consistent with IBM Cloud catalog standards.
ocofaigh
approved these changes
Dec 10, 2025
Contributor
|
🎉 This PR is included in version 1.19.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Release required?
x.x.X)x.X.x)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:
Checklist for reviewers
For mergers