![]() ![]() But if you didn’t I don’t have a compelling argument to convince you otherwise. So should you use git tags? Personally I would say it’s better to have it than not. When you check out that version in your VCS - for example, tag v1.1 or commit e35fa0d-, youre asking for a single, known set of files, and you always get the same files back. Integrating semantic-release to a CI pipeline. In git terminology, this is a 'ref', or a specific commit, which may be represented by a branch HEAD or a tag. explicit intent for commits, and automated tagging and versioning. As a result, I investigated how to version Terraform modules and ensure the approach is consistentand hopefully automated. If you’re striving to be lean, and have the barebones of what you need to get going. While an astute Terraform user could pin to a Git SHA, it is a less than ideal approach. ![]() It’s a similar argument as to why you should use a code formatter, there is more benefit to using one than not (there are definitely more reasons why you should use a code formatter). Git tags do provide a small benefit over not using them, so they’re sort of a ‘why not’. You don’t need it, you could do without it. So do you need tags in your release process? It doesn’t provide any hidden benefit, it’s just a more readable way to find a specific point in time of your codebase. So why would you use a tag instead of the commit hash? Remember a git tag is just a human readable way to read a commit hash, they’re essentially the same thing. Just the data you entered after ‘checkout’. What’s the difference between using the commit hash, or the tag? git checkout v1.2, or use the commit hash i.e git checkout d0f9b4…. Knowing that ‘version 1.1’ was stable, we can either checkout from that tag i.e. When we do that, we have two choices on how we find that previous stable release. While we’re working on fixing the issues, we checkout from the previous version and release that stable version. We need to revert to the previous version, ‘version 1.1’. Say we’ve released our second minor update, ‘version 1.2’, but we’ve found a nasty bug which has broken everything. The alternative option is to use a commit hash instead. Git tags provide a human readable way to view the codebase at a particular point in time. Git tag -a v1.2 -m 'version 1.2' But why are we creating a tag?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |