Skip to content

docs: Update badge status in README.md#586

Merged
maheshwarishikha merged 2 commits intomainfrom
maheshwarishikha-patch-1
Feb 2, 2026
Merged

docs: Update badge status in README.md#586
maheshwarishikha merged 2 commits intomainfrom
maheshwarishikha-patch-1

Conversation

@maheshwarishikha
Copy link
Member

@maheshwarishikha maheshwarishikha commented Jan 29, 2026

Description

Update badge status in README.md

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.

@maheshwarishikha
Copy link
Member Author

Readme will be updated as:

image

@maheshwarishikha maheshwarishikha merged commit 72f2ab8 into main Feb 2, 2026
@maheshwarishikha maheshwarishikha deleted the maheshwarishikha-patch-1 branch February 2, 2026 06:44
@terraform-ibm-modules-ops
Copy link
Contributor

🎉 This PR is included in version 3.2.61 🎉

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments