You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm happy to help you on release engineering. While master-commitref is probably useful for a customer or some internal project, humans want some meaningful release tags they can track, either a semer type version, or some tag name that is memorable. Sometimes people like to use a CI to generate release tags, but this is often an abuse of what tags are for. Since we treat tags as an immutable record (one cannot commit additional things to a tag), it is a great way to say,"Things were working well at X.Y.z" and this is what got put out.
Let me know if you want to go a different direction on release tagging, branches, etc.
The text was updated successfully, but these errors were encountered:
I'm happy to help you on release engineering. While master-commitref is probably useful for a customer or some internal project, humans want some meaningful release tags they can track, either a semer type version, or some tag name that is memorable. Sometimes people like to use a CI to generate release tags, but this is often an abuse of what tags are for. Since we treat tags as an immutable record (one cannot commit additional things to a tag), it is a great way to say,"Things were working well at X.Y.z" and this is what got put out.
Let me know if you want to go a different direction on release tagging, branches, etc.
The text was updated successfully, but these errors were encountered: