!next should deal with the current proposal

Question

!next should deal with the current proposal

Opened this issue 8 years ago · 1 comments

Moving to the next issue when the current proposal has not been accepted should be disallowed, somehow. Either !next should implicitly accept it (and the !accept command should go away), or !next should return an error when the current proposal has not been accepted. At the moment I prefer the former.

Answer 1 · 2016-05-06T15:42:10.000Z

Any command that advances the current issue should be affected by this, with the goal being to prevent issue advancement that would destroy the current proposal.