Add option to omit (or automatically reuse) Release xxx commits? #20
Description
As I'm still experimenting with a custom registry and publishing our workspace with various "interesting" build scripts and dependencies, publishing fails from time to time. This means smart-release has created a massive Release xxx commit with all crate names, tagged a few crates there, and then terminates until I fix the error manually.
Subsequently running smart-release after addressing the issues will create a new commit with again a lot of crate names. Would it be possible to not create this commit (maybe even automatically if the title/contents match what we're about to release) so that eventually all tags and .cargo_vcs_info.json point to the same release commit?
(I know that this is not applicable when code changes are required within my git repository - to be committed separately - but would help with spurious failures on my registry or patch bumps of related dependency crates)