-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: use the workflows for Terraform modules when updating #6
Conversation
Hey @kayman-mk! 👋 Thank you for your contribution to the project. Please refer to the contribution rules for a quick overview of the process. Make sure that this PR clearly explains:
With submitting this PR you confirm that you hold the rights of the code added and agree that it will published under this LICENSE. The following ChatOps commands are supported:
Simply add a comment with the command in the first line. If you need to pass more information, separate it with a blank line from the command. This message was generated automatically. You are welcome to improve it. |
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
This PR was closed because it has been stalled for 10 days with no activity. |
@kayman-mk This looked fine for me. Is the change still relevant? |
🎉 This issue has been resolved in version 1.1.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
The update script used the Docker workflows by accident. Changed to
terraform_module
as this repository hosts the workflows for Terraform modules.Added the
release-type
parameter. Set tomanual
so that releases are not created automatically but a PR instead.Verification
Script locally tested. Updated the workflows for the bastion host.