Eksperimental

I remember some years ago I proposed having a Markdown formatter. I think having the documentation in this format opens up the possibility to a lot of things. Now that...

I would go with one file per module per file. This way the documentation could be readable over a terminal with `less` or markdown reader.

I'm already working on it, and I have a draft working version. I will create soon an issue so we can discuss about anything related to this feature.

Here's the PR https://github.com/elixir-lang/ex_doc/pull/1992 with the Markdown implementation. You can see the generated markdown files in this repo https://github.com/eksperimental/ex_doc_markdown_formatter_docs and tell me if that would suit your needs for generating...

Thank for the fix. Unfortunately I am getting the following message in a module with no `defp` defined. ``` [R] ↘ public guard must appear before private_guard ``` The line...

Hi Rene. Thank you for looking into this. I think it is mistaking a hidden guard (public guard with `@doc false`) for a private guard. Here's a snippet that reproduces...

_That was the original reasoning behing moving the doc building to its own action._ There's an action that can filter paths on a job/step level, its this one: https://github.com/dorny/paths-filter

Yes. detecting changes with `git` is the other option to detect changes, aborting other runners I will have to look into that.

I tried to implement a solution using `git diff` but I was not really happy with it and I don't think it would cover all the cases and I felt...

I have a working version that uses `git diff`, I will be sharing it tomorrow.