Description of the limitation and why it is relevant to address
As a developer I do not want Reloading app… to be triggered after changes in the .git folder, so that I don’t have to wait for the app to be reloaded while no actual code was changed.
I think this is relevant for the VIKTOR platform because the current behavior it really annoying and waiting for no reason is boring.
When developing some long calculation, after my code changes (and waiting for the expected app reload) I’ll start the calculation in Viktor. While waiting for that I’ll select git changes to be staged and commit then. But that triggered another (unwanted) app reload.
Submitter proposed design (optional)
Ignore the .git folder, just like venv
Current workarounds
Being patient