ManageIQ Bot

Results 1193 comments of ManageIQ Bot

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 commit https://github.com/jrafanie/manageiq-schema/commit/7748a2f615c2d7b51297880b995155944bfb0756 with ruby 2.7.8, rubocop 1.56.3, haml-lint 0.51.0, and yamllint 2 files checked, 54 offenses detected **db/migrate/20240228190145_add_column_defaults.rb** - [ ] :exclamation: - [Line 10](https://github.com/jrafanie/manageiq-schema/blob/7748a2f615c2d7b51297880b995155944bfb0756/db/migrate/20240228190145_add_column_defaults.rb#L10), Col 5 - [Style/MethodCallWithArgsParentheses](https://docs.rubocop.org/rubocop/1.56/cops_style.html#stylemethodcallwithargsparentheses)...

This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the `stale`...

Checked commit https://github.com/jaywcarman/manageiq-schema/commit/a69ff4e92f28082cd3452ec5789148253175be59 with ruby 2.6.10, rubocop 1.28.2, haml-lint 0.35.0, and yamllint 2 files checked, 0 offenses detected Everything looks fine. :+1:

This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the `stale`...

This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the `stale`...

This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the `stale`...

This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the `stale`...

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...