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
Tags in Git serve as a means to designate significant moments in your repository's history. They are commonly employed to indicate release versions, such as v1.0, v2.0, and so on.
I suggest utilizing branches with the following naming conventions to handle releases:
release-1.1
release-1.2
release-2.1
It's worth noting that the k8s-device-plugin and other projects have already implemented this approach successfully.
The text was updated successfully, but these errors were encountered:
Tags in Git serve as a means to designate significant moments in your repository's history. They are commonly employed to indicate release versions, such as v1.0, v2.0, and so on.
I suggest utilizing branches with the following naming conventions to handle releases:
release-1.1
release-1.2
release-2.1
It's worth noting that the k8s-device-plugin and other projects have already implemented this approach successfully.
The text was updated successfully, but these errors were encountered: