juniper
juniper copied to clipboard
Automatic injection of version information into the docs.
Hello folks,
I propose to tweak the documentation generation process generally according to the following rules:
- If a commit has a tag like "juniper-n.n.n" then use that tag as the version in the docs. Else use the first few digits of the commit hash as the version.
With a bit of reflection I think you can easily see that given this change any commit that you think is worthy of having a release tag thereby has the conventional semver-friendly release specified in the docs, whereas any other commit uses an unambiguous commit hash.
IMHO of course. What say anybody else?