Iterative code update generation

[roryeckel]

Hello,
This is a very interesting project. I have an idea: iterative documentation generation.
For example, when codewiki generates its documentation, the commit hash can be stored in the output.
Then, we could invoke some regeneration command, and it will build upon the existing documentation considering the commits made since the last stored hash.
This could improve usefulness in production scenario.
Opinions?

[anhnh2002]

What a thoughtful suggestion, thank you for sharing it!

We’ve actually been planning to support incremental CodeWiki documentation updates based on code changes, very similar to what you described with storing the commit hash and regenerating from there.

That said, all of the current maintainers are quite busy at the moment, so we probably won’t be able to work on this in the immediate future. Our rough plan is to revisit and implement this within the next three months.

In the meantime, we’d really appreciate it if you’d like to open a PR to help move this forward. Your contribution and ideas would be very welcome!