> Since the services are not a single file, it is not user-friendly to download directly from the Repo if the files are not zipped. I think you're conflating t

> Since the services are not a single file, it is not user-friendly to download directly from the Repo if the files are not zipped. I think you're conflating two separate things, source code and a packaged releases. The Github repository should have the source code, which in your case is the XML code for the workflow and plist. You then create a release [1] from that software. It's usually customary to include the script used to build it, which in this case is likely just a shell script wrapper around the zip command to create the archive. The important point is that the source is always visible. Uploading zip files into the repo gives the impression that you're trying to hide something, even if that isn't the case. Also, one of the great things about open source is that people can be curious. It's likely that if you had checked in the unzipped files, people would have browsed through them in the Github UI to see how it worked. Fewer people will take the time to clone the repo or download/unzip/browse the zip file. [1] https://github.com/blog/1547-release-your-software https://github.com/blog/1547-release-your-software