Another interesting thing I've found is that packagers really prefer tarballs. They can checksum them. They don't need to download your full history, etc.
The tarballs automatically produced by github have names that are annoying and makes things harder for packagers, so I find myself creating "make dist" targets and uploading the result to github. Is there an API for file uploads? (that would be sweet!)
I do wish there was a way to provide a format string that would tell github the basename to use for tarballs.
If you are jquery and your project is jquery your tarballs look like jquery-jquery-v1.2.3-g654321.tar.gz and the directory basename is the same.
If they added the ability to configure it per-repo and used "{{ user }}-{{ repo }}-{{ tag }}-{{ sha1 }}" as the default then they could keep backwards compat and let folks configure it to their liking. It's one of my very few github peeves.
If there existed a git-next tool to document that workflow then it might be more widely known, I guess. There probably is no tool because it's all just normal git stuff.
The document mentions:
- The tip of 'master' is meant to be more stable than any
tagged releases, and the users are encouraged to follow it.
To me, wikis just seem 'lazy'. Projects that use wikis as a primary form of documentation make users feel like the project is un-cared for, and not worth documenting.
I have absolutely no stats to back this up--but having officially written documentation gives projects a really good 'feel', and makes it a lot simpler for users to get started (IMO).
The tarballs automatically produced by github have names that are annoying and makes things harder for packagers, so I find myself creating "make dist" targets and uploading the result to github. Is there an API for file uploads? (that would be sweet!)
I do wish there was a way to provide a format string that would tell github the basename to use for tarballs.
If you are jquery and your project is jquery your tarballs look like jquery-jquery-v1.2.3-g654321.tar.gz and the directory basename is the same.
If they added the ability to configure it per-repo and used "{{ user }}-{{ repo }}-{{ tag }}-{{ sha1 }}" as the default then they could keep backwards compat and let folks configure it to their liking. It's one of my very few github peeves.