Tagnotate tags code#I need some way to make sure that the code that’s being rolled out in the current project is approved and stable. If i review a project, I only see the composer.lock file, but don’t immediately see the code for the actual module. We write modules in separate modules, and include those modules using composer in actual projects. To elaborate, here are three viable use cases: Whodunnit You should care about the advantages of annotated tags. If you need to amend / fix / replace an existing tag, you can use the -f parameter to overwrite the current tag.$ git tag -s -a -m "JIRA-11: Include your tag message here" 0.12.0 Read this StackOverflow answer to see why, because I can’t explain it any clearer than that :) So, which one should I use? The short answer is annotated tags. You can add a tag message, GPG sign it, and the tagger is stored. This tag allows you to store information that is related to this specific tag. Annotated tags: A tag that has its own commit hash and is, as such, stored as a separate object in git.This type of tag does not allow you to store any information that specific to the tag. This merely functions as a pointer to a specific commit, and as such it ‘piggybacks’ on that commit’s hash as identification. Lightweight tags: A tag that is attached to an existing commit.This is all due to the fact that there are two distinct types of tags in git: So, what’s the difference then? The answer is that there are two distinct types of tags.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |