-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mdbook build
flag that doesn't implicitly create files and errors if bad path in SUMMARY.md
#253
Comments
Seems good to me. |
Yes, sounds good! |
frewsxcv
referenced
this issue
in frewsxcv/mdBook
Apr 18, 2017
Opened a PR: https://github.com/azerupi/mdBook/issues/254 |
frewsxcv
referenced
this issue
in frewsxcv/rust
Apr 27, 2017
This will avoid obscure Travis CI error messages: * rust-lang#40290 (comment) Original mdbook issue: * https://github.com/azerupi/mdBook/issues/253 mdbook PR: * https://github.com/azerupi/mdBook/pull/254
frewsxcv
referenced
this issue
in frewsxcv/rust
Apr 27, 2017
Bump mdbook dep to pick up new 'create missing' toggle feature. This will avoid obscure Travis CI error messages: * rust-lang#40290 (comment) Original mdbook issue: * https://github.com/azerupi/mdBook/issues/253 mdbook PR: * https://github.com/azerupi/mdBook/pull/254
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For rustc's CI, we set the filesystem to be mostly read-only. If a rustc docs contributor accidentally adds in an invalid path, we get these obscure read-only errors because mdbook is trying to create a file even though we don't want it to. It'd be helpful if there was a
mdbook build
flag like--nocreate
or--strict
that doesn't attempt to create files from SUMMARY.md if they don't exist and instead results in a build error.Does this sound alright? If so, I can implement this.
The text was updated successfully, but these errors were encountered: