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
By state, I mean being able to refer to a specific commit in the history of a repo. I want to be able to track any given epub back to the asciidoc source and travis config.
I wrote this up in our documentation on using semantic versioning. This can be done with the metadata _version key and a git tag. This would be good enough for now.
Later on we can do things like grabbing the git commit hash from the repo or even generating a checksum of the repo's contents. Ideally we would also maintain our own clones of the sources we use during build (like HTMLBook) and have a version number specified for each. But that can come later.
❗ We need a stamp on outgoing books that lets us know the state of the git repo that built it.
HTMLBook
andasciidoctor-HTMLBook
that we clone during travis build.The text was updated successfully, but these errors were encountered: