Update rubygem-hammer_cli_foreman_remote_execution to 0.3.2 #11774
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
error: Installed (but unpackaged) file(s) found:
/usr/share/gems/gems/hammer_cli_foreman_remote_execution-0.3.1/.github/workflows/ci_test.yml
/usr/share/gems/gems/hammer_cli_foreman_remote_execution-0.3.1/.rubocop_todo.yml
Installed (but unpackaged) file(s) found:
/usr/share/gems/gems/hammer_cli_foreman_remote_execution-0.3.1/.github/workflows/ci_test.yml
/usr/share/gems/gems/hammer_cli_foreman_remote_execution-0.3.1/.rubocop_todo.yml
I think there are 2 solutions to this: exclude them in the spec or stop shipping them in the gem. I think the latter is cleaner, but will require a new release.
Any preference from your side?
I'll remove them from gemspec and release a new version :/ |
I wonder if this is something we'll see in more gems and we should standardize the files it includes between our plugins. |
It just happens, but mostly with older? plugins. This plugin uses UPD: It's even worse than that... We need to do some housekeeping in the repo and in the rpm spec. I'd close this PR... |
If you release a new version the bot will update this PR with the new version. No need to close it IMHO. Because of #11782 it will get rewritten, which may or may not be a good thing. |
github-actions
bot
changed the title
github-actions
bot
force-pushed
the
bump_rpm/rubygem-hammer_cli_foreman_remote_execution
branch
from
2709bcb to
7445bad
Compare
It did indeed 🚀 |
ofedoren
deleted the
bump_rpm/rubygem-hammer_cli_foreman_remote_execution
branch
No description provided.