ManageIQ Bot
ManageIQ Bot
Checked commit https://github.com/miq-bot/manageiq/commit/8f836f2ccdd2d8502570f3b154e1b1225ffa344a with ruby 2.7.8, rubocop 1.56.3, haml-lint 0.51.0, and yamllint 0 files checked, 0 offenses detected Everything looks fine. :trophy:
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release...
Checked commits https://github.com/kbrock/manageiq/compare/4150ce6482730999b8909fa2af9ca03905e34047~...ddf44703044041f55d6859e6552ebdcef19063ae with ruby 3.1.5, rubocop 1.56.3, haml-lint 0.51.0, and yamllint 3 files checked, 2 offenses detected **lib/miq_expression.rb** - [ ] :exclamation: - [Line 335](https://github.com/kbrock/manageiq/blob/ddf44703044041f55d6859e6552ebdcef19063ae/lib/miq_expression.rb#L335), Col 11 - [Style/HashTransformValues](https://docs.rubocop.org/rubocop/1.56/cops_style.html#stylehashtransformvalues)...
Checked commit https://github.com/GilbertCherrie/manageiq/commit/0d4de869595aff5eaa367caf86aaa5b904679284 with ruby 2.7.8, rubocop 1.56.3, haml-lint 0.51.0, and yamllint 0 files checked, 0 offenses detected Everything looks fine. :cookie:
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release...
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release...
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release...
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release...
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release...
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release...