On the first invocation of log4brains build after adding a new ADR markdown doc, an HTML version of that doc is not created in the .log4brains/out/adr directory. On subsequent invocations of log4brains build, the HTML doc is correctly generated.
Steps to Reproduce
Create a new markdown file in docs/adr
Run log4brains build
Observe that .log4brains/out/adr does not contain an HTML file matching the name of your markdown file
Run log4brains build
Observe that .log4brains/out/adr does contain an HTML file matching the name of your markdown file
Expected Behavior
All markdown files should be compiled into HTML on the first invocation of log4brains build.
Context
We notice this in CI (Github Actions), which is generally the first time we run log4brains build. But it is reproducible locally on MacOS 10.15.
Environment
Log4brains version: 1.0.0-beta.11
Node.js version: 14.15.4
Yarn version: 1.22.10
OS and its version: Reproducible on MacOS 10.15 and Ubuntu 20.04 (via GitHub Actions)
Bug Report
Description
On the first invocation of
log4brains buildafter adding a new ADR markdown doc, an HTML version of that doc is not created in the.log4brains/out/adrdirectory. On subsequent invocations oflog4brains build, the HTML doc is correctly generated.Steps to Reproduce
docs/adrlog4brains build.log4brains/out/adrdoes not contain an HTML file matching the name of your markdown filelog4brains build.log4brains/out/adrdoes contain an HTML file matching the name of your markdown fileExpected Behavior
All markdown files should be compiled into HTML on the first invocation of
log4brains build.Context
We notice this in CI (Github Actions), which is generally the first time we run
log4brains build. But it is reproducible locally on MacOS 10.15.Environment