Coverage decreased (-2.4%) to 88.107% when pulling 6fd8f82476f3884bd0ce5ca76612bd57de089d46 on atoomic:git-alarm into 95d93019b511ff0119dffaeab229502dab262152 on metacpan:master.
Coverage decreased (-2.4%) to 88.107% when pulling 6fd8f82476f3884bd0ce5ca76612bd57de089d46 on atoomic:git-alarm into 95d93019b511ff0119dffaeab229502dab262152 on metacpan:master.
Coverage decreased (-2.4%) to 88.107% when pulling 6fd8f82476f3884bd0ce5ca76612bd57de089d46 on atoomic:git-alarm into 95d93019b511ff0119dffaeab229502dab262152 on metacpan:master.
Case: GH #50
There was already an alarm set aroun the "git run" command but nothing was killing the "git" command running behind.
When the alarm is triggered check if we have a running git command, if so, try to kill it.
Also guarantee that the alarm timer is always set (0 is invalid)