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
The idea is to use a standardized set of commit message prefixes so that candidates for cherry-picks to a patch or minor version can be then selected automatically.
As an example, everything that was committed after a branching point that has a fix: commit message prefix may be cherry-picked to a minor release branch.
This convention forces everyone to make some of the decisions when the commit is being made, therefore when the knowledge is fresh in the mind.
I am not sure what happens if you commit a malformed message. Maybe some enforcement git-precommit script is required to avoid the situation.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The idea is to use a standardized set of commit message prefixes so that candidates for cherry-picks to a patch or minor version can be then selected automatically.
https://www.conventionalcommits.org/en/v1.0.0/
As an example, everything that was committed after a branching point that has a
fix:
commit message prefix may be cherry-picked to a minor release branch.This convention forces everyone to make some of the decisions when the commit is being made, therefore when the knowledge is fresh in the mind.
I am not sure what happens if you commit a malformed message. Maybe some enforcement git-precommit script is required to avoid the situation.
Beta Was this translation helpful? Give feedback.
All reactions