3 ms·

This is what I do except I use a shell script instead of a Makefile. A working example of this is at: https://github.com/nickjj/docker-flask-example/blob/91238

by nickjj 4y ago

This is what I do except I use a shell script instead of a Makefile. A working example of this is at: https://github.com/nickjj/docker-flask-example/blob/912388f31f5cae03499dc82e2139e7c8f4b3168c/.github/workflows/ci.yml#L19-L29 https://github.com/nickjj/docker-flask-example/blob/912388f3... Those ./run ci:XXX commands are in: https://github.com/nickjj/docker-flask-example/blob/912388f31f5cae03499dc82e2139e7c8f4b3168c/run#L144-L179 https://github.com/nickjj/docker-flask-example/blob/912388f3... I like it because if CI ever happens to be down I can still run that shell script locally.

sneak 4y ago
You should still have a Makefile that calls your shell scripts when "make" or "make test" is run. Every person who writes shell scripts has a different filename and arguments. "make" and "make test" are always the same everywhere.