Quote:
Originally Posted by dhdurgee
I am uploading it here as github would not accept a zip file, strange omission there.
|
It's not an omission.
If you had uploaded the sox directory and all its contents, made a commit, and tagged that commit as something like v0.1 github would consider that commit a release. (github uses some heuristic to decide whether a tag name is a release.) Interested people can download any release as a zip or tar.gz at their choice without having to clone the repository.
If you make a change to playfile.sh in the git working tree on your computer and have tested it and are ready to release, it can be as simple as:
Code:
git commit -a
git tag v0.2
git push
git push --tags
(You might get prompted for username and password, depending on how your github account and local git are configured.)
Boom. You just made a new release and didn't have to zip anything up, clean up your working tree, only uploaded changes to a file, and didn't have to muck around in a web browser getting the file to the correct place.
And collaborators can do a git pull and only sox/playfile.sh and their repository clone change on their systems, and they can easily see what the changes were.
To reiterate, github automatically packages up up releases and releases are published by simply appropriately tagging a commit.