Sign in to confirm you’re not a bot
This helps protect our community. Learn more

What Is a Release

1:04

The Structure of Semantic Versioning

4:05

Types of Git Tags

7:43

Annotated Tags

8:34

Benefits of Using Semantic Releases in a Git Repository

10:29

Semantic Versioning for Your Git Tags

11:16

Creating a Semantic Git Release Using Annotated Tags and Semantic Versioning

13:14

Creating a Semantic Release Uh Use Tag Using Command Line

13:45

Creating a Semantic Release Using Tools like Get Kraken

14:25

Create an Annotated Tag

14:44

Release Notes

15:25

Recommended Actual Minimums for an Annotation

16:23

Private Projects

17:38

Commit Messages

18:03

Extra Credit

19:54

View Release Notes

21:24

Takeaways from this Presentation Semantic Versioning

25:27

Patch Releases

25:46

Naming Your Annotated Tags with Semantic Version Numbers

26:43

Resources

27:58

Does It Make Sense To Add Generated Tags as Special Comments in Source Code

32:04

What's the Actual Syntax in the Git Log

35:33

Github Actions

40:01

For Repos That Have Never Had any Standard Versioning and Also a Few Users Is It Reasonable To Go Back in Time and Add Versioning as Appropriate

41:40
How to Manage Releases with Semantic Versioning and Git Tags
416Likes
32,708Views
2021Nov 12
Being able to easily manage and communicate changes in code releases is fundamental to the long term success of teams and projects using Git. Using a standard versioning system, such as semantic versioning with Git, and knowing how to use Git tags to easily tag a repository with a proper release number, helps teams easily manage their growing product. Watch this GitKon Git conference session by Michael Miles from MIT Sloan to learn more about semantic versioning and Git. Learn about the GitKraken Git client and download free: https://bit.ly/3iiqM5x Speaker: Michael Miles Director of Web Development, MIT Sloan   / mikemiles86  

Follow along using the transcript.

GitKraken

32.2K subscribers