Closed chrisridd closed 12 years ago
Good idea - I'll bump the version # and upload the latest code tomorrow.
It might be worth fixing the -creators method first, just to avoid putting crud into the initial Spotlight index. (Fixable afterwards, but...)
I'd suggest tagging the repo using "git tag
I've put v1.4 of the qlgenerator in the download section (code as 030ecd7b4d7113721c6766a23aee1f6182dbae0e). The tags I've entered via git tag
don't seem to be making their way to github (syncing with the GitHub.app) though, not sure what I'm missing…
Cool! WRT the tags you might have to use git from the command line. A normal "git push" doesn't push tags, and that might be what GitHub.app is doing.
Aha - a git push —tags
did the job - wish I'd noticed this before overwriting all my local tags a while ago though.
Excellent. Might be worth asking for GitHub.app to do the right thing :-)
At some point it is probably worth tagging a new release and putting up a new download file.