search

convissor / login-security-solution

Development of the login-security-solution WordPress plugin happens here.
33 stars 21 forks source link

tagging releases #19

Closed cfoellmann closed 11 years ago

cfoellmann commented 11 years ago

Hi @convissor, could you please tag the releases for easier access?

Thx, @cfoellmann

convissor commented 11 years ago

I'm familiar with tagging. I've used it on several projects. I hadn't used it here because Github is just a spot to manage history and workflow. The releases go out from wordpress.org. Thus far this has been a solo project with a small code base.

Releases are based off of the commits having the message Release #.##.# on Github. The commits are squashed on wordpress.org so each commit is one release.

In git, it's pretty easy to make a branch and/or checkout from a particular "Release" commit if you want to.

How would tagging help you?

cfoellmann commented 11 years ago

I would love to deploy the plugin directly from the repo. Tags should not contain files unnecessary for production use like phpunit tests. Thereby I could deploy the tag as I always do and reduce clutter on my environment.

convissor commented 11 years ago

Tags are essentially an indicator of the version of each file in the repository at a given point in time. The tags would contain the unit tests. The unit tests are part of the releases. If you don't want the unit tests in your production code you'll have to come up with a system to do that. Perhaps create a branch and rm the tests dir.

cfoellmann commented 11 years ago

Maybe I will create some script for git or sth. Tags would be great still