Reputation
290
Top tag
Next privilege 300 Rep.
Create new tags
Badges
3 11
Impact
~7k people reached

  • 0 posts edited
  • 0 helpful flags
  • 15 votes cast
Jun
18
awarded  Notable Question
May
19
awarded  Notable Question
Jan
23
awarded  Self-Learner
Aug
29
awarded  Popular Question
Feb
19
awarded  Popular Question
Oct
24
awarded  Yearling
Jul
3
awarded  Revival
Jul
3
accepted git tagging comments - best practices
Jul
3
answered git tagging comments - best practices
May
29
comment What's the right way to work with a graphic designer?
mistakes get made, just make sure you learn from them, in general, try to keep things as simple as possible while staying modular :)
May
29
awarded  Commentator
May
29
comment git tagging comments - best practices
Thanks aviv - what would you suggest putting into a tag comment? I want to try to avoid putting redundant information in there.
May
29
awarded  Editor
May
29
revised git tagging comments - best practices
added 207 characters in body
May
29
comment git tagging comments - best practices
It keeps all releases well documented; it's easy to compare changes between tags as opposed to having to dig through commits that do not always represent releases. It also makes it easy to "roll back" to the last release if necessary. An example of this can be found here: github.com/osCommerce/oscommerce2/tags but in this example, the comments are more or less the same as the tags. I'm looking for a better system to fully maximise the utility of the comments
May
29
comment git tagging comments - best practices
I'm not sure I follow - each of these bug fixes may contain multiple commits (not necessarily for bug fixes, but certainly for features). Bug fixes need to be pushed to production, and thus it seems necessary to tag them, no?
May
29
answered What's the right way to work with a graphic designer?
May
29
asked git tagging comments - best practices
May
25
awarded  Teacher
May
24
answered Designing a SQL-like encapsulation object for programmatic use