This would probably be quite a headache to handle, but it would be super nice to create a mirror having 2 (or n) dependencies by running pre-commit-mirror path-to-mirror ruby gem1,gem2 '\.rb' for example.
The use case I came across is using rubocop-rspec with rubocop. It basically consists in running rubocop with --require rubocop-rspec but needs to have the rubocop-rspec gem installed as well.
Right now I manage to get some work around by first generating the mirror, then adding the dependency to the second gem as a new commit and then rewrite the commit history order to move that commit to the beginning. But the process breaks the tags with are not in the master branch anymore, is quite painful, and doesn't work if we want to be able to select a "matrix" of versions.
Do you think it's worth investigating further?
This would probably be quite a headache to handle, but it would be super nice to create a mirror having 2 (or n) dependencies by running
pre-commit-mirror path-to-mirror ruby gem1,gem2 '\.rb'for example.The use case I came across is using
rubocop-rspecwithrubocop. It basically consists in running rubocop with--require rubocop-rspecbut needs to have therubocop-rspecgem installed as well.Right now I manage to get some work around by first generating the mirror, then adding the dependency to the second gem as a new commit and then rewrite the commit history order to move that commit to the beginning. But the process breaks the tags with are not in the master branch anymore, is quite painful, and doesn't work if we want to be able to select a "matrix" of versions.
Do you think it's worth investigating further?