id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 29026,Make makemigrations scriptable / script-friendly,Chris Jerdonek,Jacob Walls,"Currently, the `makemigrations` management command doesn't lend itself well to scripting. For example, it writes its progress output to `stdout` rather than `stderr`. Also, there doesn't appear to be a structured / programmatic way to figure out what files it has created. My use case is that in my development environment, I'd like to be able to run `makemigrations` in a Docker container, find out what files were added (e.g. from `makemigrations`'s output), and then copy those files from the Docker container to my development machine so they can be added to source control. Currently, there doesn't seem to be an easy way to do this. One way, for example, is to manually read `makemigrations`'s output to find out what apps were affected, and then inspect the directories yourself for the new files. Better, for example, would be if `makemigrations` could write the paths to the created files to `stdout`. ",New feature,closed,Migrations,dev,Normal,fixed,"makemigrations,scripting,stderr,stdout",,Ready for checkin,1,0,0,0,0,0