Currently, miss-islington use of cherry-picker is aborting the cherry pick in case of conflicts. This doesn't work because self.initial_state is not being updated after conflicts are discovered by cherry-picker, and so the abort is raising a ValueError from the guard at the start of abort_cherry_pick().
Since self.initial_state is only used for those guards, let's just remove it and read from .git/config every time.
Currently,
miss-islington
use ofcherry-picker
is aborting the cherry pick in case of conflicts. This doesn't work becauseself.initial_state
is not being updated after conflicts are discovered bycherry-picker
, and so the abort is raising a ValueError from the guard at the start ofabort_cherry_pick()
.Since
self.initial_state
is only used for those guards, let's just remove it and read from.git/config
every time.