Environment
- OS: Windows 11 24H2 Insider (Build 26120.3073)
- Dotter version: v0.13.3
- Using Rust 1.84.1 compiled version
Description
When using watch mode, the rendering of post-deploy hook to the cache seems to be caught by watchexec, despite the filter implemented (This filter is also now deprecated by watchexec). Ā Because hook rendering always happens during a deploy, it causes a loop where each hook render creates a new watchexec event which creates a new hook render, etc.
Reproduction
- Create a simple dotter repo with a simple post-deploy hook
(i.e. echo "Hook ran")
- Run
dotter watch
Expected behavior
dotter watch should only retrigger when files in the dotfiles repository are changed except for the cache files (which do change when rendering hooks/templates)
Actual behavior
dotter watch likely detects a change in the cache or something, but infinitely redeploys. This includes rerunning the deploy script.
Environment
Description
When using watch mode, the rendering of post-deploy hook to the cache seems to be caught by
watchexec, despite the filter implemented (This filter is also now deprecated bywatchexec). Ā Because hook rendering always happens during a deploy, it causes a loop where each hook render creates a newwatchexecevent which creates a new hook render, etc.Reproduction
(i.e.
echo "Hook ran")dotter watchExpected behavior
dotter watchshould only retrigger when files in the dotfiles repository are changed except for the cache files (which do change when rendering hooks/templates)Actual behavior
dotter watchlikely detects a change in the cache or something, but infinitely redeploys. This includes rerunning the deploy script.