The upcoming official Habari addons directory will be using a post-receive hook on Github repositories, and we'd like to use tagging to identify released versions of plugins and themes, such that an 0.8-1.0 version of a particular plugin (denoting that it is version 1.0 of the plugin for Habari 0.8.x) would be available, and identified as such.
Despite having some experience now with moving code around using git and Github, I haven't gotten the hang of tagging so much yet. The existing post-receive hook code (http://github.com/mikelietz/post_receive) is able to identify a tagged commit, but in testing (often by hitting the 'test hook' button rather than pushing commits) I haven't really seen how/when a tag comes across. Also, it seems the default is to not push tags to the remote repository at all. These are just things I've seen, and may not be representative of how tagging works in the real world. Anybody have good experience with tagging and could shed some light on a possible best practice? mikelietz -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev
