Timeline for answer to Should generated documentation be stored in a Git repository? by Paŭlo Ebermann
Current License: CC BY-SA 4.0
Post Revisions
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2019 at 13:57 | comment | added | ANone | This doesn't have to be at the commit stage. It could easily be a downstream/CI/Jenkins job to publish them every time they are deemed worthy of storage. This may well be each commit, but the decision should be decoupled in the absence of a good reason. Or at least that's the way I see it. | |
| May 14, 2019 at 11:10 | comment | added | cmaster - reinstate monica | That would pretty much require a pre-commit hook in each and every repo that is used to create commits. Because if the documentation generation process is not fully automated, you will get commits that have the documentation out-of-sync with the code. And those broken commits will hurt understandability more than uncommitted documentation. | |
| May 13, 2019 at 22:47 | history | answered | Paŭlo Ebermann | CC BY-SA 4.0 |