On Tuesday 20 October 2015 19:51:36 Marc Tamlyn wrote: > I see what you mean and the inherent problems with the design. However > fundamentally the command you are running is "make some migrations", and > the "I don't have any to make" step is clearly an error case, not a success > case. In particular it would be very wrong for the real "I want to make > some migrations" command to return a non-zero code when it does > successfully create some. > > The only real solution I can see is a separate command, or something like > makemigrations --check.
Agreed. In particular, > On 20 October 2015 at 05:20, Jon Dufresne <[email protected]> wrote: > > > > It seems exit status 1 is overloaded to mean "all migrations are > > accounted for, continue to the next stage of CI", and "something went > > terribly wrong". > > No; it seems the "makemigrations" command is overloaded to mean both "make migrations for me" and "verify that no migrations need to be made". HTH, Shai.
