Mathieu Barbin

https://github.com/ocaml/odoc/pull/784#discussion_r756772278 +1 about this. I think it would be a great user improvement to hide the warnings that are not actionable (internals) from the user, and especially these that print...

Hi @EmileTrotignon Thank you for your response :smiley: ## doc-new Thanks for letting me know about it, I had missed it. Earlier today I attempted to build a doc with...

Just to bring up another (unrelated?) issue that's been adding to my confusion: there are warnings that still pop up and don't cause `dune build @doc` to fail, even when...

Thank you so much for looking into my build issue, @art-w, and for publishing a working build! That's really kind of you. The `@doc-new` mode seems like a very useful...

> I vaguely remember reading about this issue somewhere, but can't recall where exactly. For now, I've been ignoring them (without trying to filter them out) in the hope that...

Thank you for your response, @emillon ! I understand what you are saying about `(mode promote)` working as intended. My issue is simply with how it interacts with my CI...

Result from the experimentation in [this PR](https://github.com/mbarbin/bopkit/pull/9) I switched the CI to include the `git diff --exit-code` extra step: ```yml - name: Run tests run: | opam exec -- dune...

> I will consider switching to this CI pattern more globally in my repos. I wanted to report that I enabled a similar check for rejecting uncommitted changes as part...

I wanted to link a live example of the issue for reference: https://github.com/mbarbin/vcs/pull/2 In this PR, I've worked around the module name conflict by renaming the vendored libraries and prefixing...

:information_source: This PR is intended to be closed, as its changes are likely to be subsumed by PR #56 and any subsequent related PRs.