You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, great tool, thank you for making it. I do have one concern, though - some repositories I work on have extensive pre-commit scripts that do things like run the entire test suite and ensure that nothing fails. This would probably cause Dura's commits to fail as tests are more often than not broken while new code is being written.
I'm not familiar with Rust myself, but I'm not sure if git2's commit function supports the --no-verify flag, or if it skips git hooks by default.
The text was updated successfully, but these errors were encountered:
Have you tried dura yet? This SO answer suggests to someone that they use libgit2 instead of Git for this exact reason. Can you verify that it does this?
FWIW I pushed a commit last night that writes JSON logs to ~/.config/dura/logs. You could look at the latency left in these logs, or you could just leave the dura serve window open.
Hey, great tool, thank you for making it. I do have one concern, though - some repositories I work on have extensive pre-commit scripts that do things like run the entire test suite and ensure that nothing fails. This would probably cause Dura's commits to fail as tests are more often than not broken while new code is being written.
I'm not familiar with Rust myself, but I'm not sure if git2's commit function supports the
--no-verify
flag, or if it skips git hooks by default.The text was updated successfully, but these errors were encountered: