You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that your Consul module ships with all of the module fixtures intact. This caused a minor problem for me as there are .git directories in the fixtures that cause submodule warnings when pushing/pulling this module from git via an r10k workflow, but it also means your module is shipping redundant/unused copies of the stdlib and archive modules so the download size of your module is bigger than it needs to be.
Would you be against adding a step somewhere in the build process to clean these out prior to building the module tarball?
The text was updated successfully, but these errors were encountered:
I noticed that your Consul module ships with all of the module fixtures intact. This caused a minor problem for me as there are
.git
directories in the fixtures that cause submodule warnings when pushing/pulling this module from git via an r10k workflow, but it also means your module is shipping redundant/unused copies of the stdlib and archive modules so the download size of your module is bigger than it needs to be.Would you be against adding a step somewhere in the build process to clean these out prior to building the module tarball?
The text was updated successfully, but these errors were encountered: