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
Usage of "conventional commits" format, which is the standard in terms of version control management for software and engineering projects in general, could be beneficial to browse or check the history of a repo: https://www.conventionalcommits.org/en/v1.0.0/#summary
It's more a nice-to-have, of couse, but also a very small effort which can bring value.
The text was updated successfully, but these errors were encountered:
I already wondered whether we should try out such a convention, preferably while working on a (reatively) fresh project.
I'm not sure retrofitting the convention to an almost completed one like SDF-base will be so useful.
(In any case, we'd need to document what specific set of choices applies to an Internet-Draft/RFC development.)
Usage of "conventional commits" format, which is the standard in terms of version control management for software and engineering projects in general, could be beneficial to browse or check the history of a repo: https://www.conventionalcommits.org/en/v1.0.0/#summary
It's more a nice-to-have, of couse, but also a very small effort which can bring value.
The text was updated successfully, but these errors were encountered: