Reading the build_tarball(...) function in planemo/shed.py used in the command planemo shed_upload, currently it appears to essentially collect all the files under the given path.

This should work fine where you have .../my_tool/test-data/ and .../my_tool/tool-data/ under .../my_tool/ as used on https://github.com/galaxyproject/tools-devteam/ and https://github.com/galaxyproject/tools-iuc and https://github.com/bgruening/galaxytools

This will not work where there is a common test-data/ and tool-data/ folder used by multiple tools, as on https://github.com/peterjc/galaxy_blast and https://github.com/peterjc/pico_galaxy

Maybe I should re-arrange my folder structure, but an alternative would be extending the build_tarball(...) function to allow this to be configured, perhaps with a manifest (white list of files to include)? Perhaps this could go in the .shed.yml file (see #25)?

See also #24 which would allow a workaround allowing the tar-ball to build outside of the planemo shed_upload command.