![]() On the other hand, if the environment is on a branch that is 14 commits ahead of the last tag, `git describe` will return something like this: $ git describe ![]() Otherwise, it shows the tag name appended with the number of additional commits and the abbreviated SHA of the current commit.įor example, if the environment is on a commit tagged 1.0.4, `git describe` will return that exact tag: $ git describe If the tag is on the current commit, then only the tag is shown. The `git describe` command finds the most recent tag that is reachable from a commit. This is why the `git describe` command exists. End user applications can also benefit from semantic version tags.Ī project that is using tags isn’t always going to be on a tagged commit. Git tags in concert with semantic versioning are the critical ingredients for modern dependency management tools such as Composer, but they also can be used for team communication about more than just library code. Git Tags provide an excellent, direct, and simple way to mark the code when a specific version gets released during the development life cycle. Git has a feature called Tags, which is compatible with semantic versioning. This standard emerged to support the growing popularity of dependency management systems, such as Composer, which require a consistent way of handling version dependencies. The official spec for semantic versioning is published at Git Tags Semantic versioning is a simple set of rules and requirements that dictate how version numbers are assigned and incremented. To implement this, let’s review three important ingredients: We’ll take a look at some simple steps that can be added to any build process, which automate the sharing of the semantic version in every environment. Taken together, semantic versioning and git tags have been terrific tools for developers, but are not always of immediate value to the rest of a project team and the users, making issue tracking more cumbersome and imprecise. This is a great way to mark the semantic versions on a project. Git tags are specific points in the Git history that are designated as being important. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |