[x] Tagging last known working code (ex: tested_3_13_2017)
[x] Tag code after each day of competition (ex: end_of_kettering_day_one)
This will help should an issue come up (ex: current code's no good, let's go back to what we were using at kettering, this makes it drop dead easy to find the code used at kettering).
Tags will show up in sourcetree like so (see label "3"):
WARNING
Unlike branches, consider tags to be PERMANENT. Although it is possible to remove them, it becomes a pain if anyone already has the tag.
How to tag:
Take a look at SirLancebot's tags. In particular, consider:
This will help should an issue come up (ex: current code's no good, let's go back to what we were using at kettering, this makes it drop dead easy to find the code used at kettering).
Tags will show up in sourcetree like so (see label "3"):
WARNING
Unlike branches, consider tags to be PERMANENT. Although it is possible to remove them, it becomes a pain if anyone already has the tag.