Allow flags for commit message driven execution

[JayjeetAtGithub]

Addresses #696

[pep8speaks]

Hello @JayjeetAtGithub! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2019-07-10 05:37:38 UTC

[JayjeetAtGithub]

@ivotron I was using action argument to take both action and workflows, but on moving ahead with that I found that it increased the complexity of the code very much, because of a large number of type checkings, if else, etc. Same was the case with --skip taking workflows.

So I was thinking if we could keep the --wfile flag intact and just make it multiple=True. Also we can change the action argument to a flag --action instead. It would be very helpful, if you could review the current PR and also please give your thoughts upon this. Thanks.

[ivotron]

I see. The main problem I see with allowing multiple occurrences of --wfile is that all other arguments (except --recursive) assume there's only one workflow being executed. For example --skip or --on-failure, etc..

One alternative we have is to go with the original plan of supporting multiple occurrences of the popper:run[...] keyword, and run as many times as this is shown. If we do this, we could deprecate --wfile and parse the positional argument with the following criteria: if there's a file with that name, then assume it's a workflow, otherwise assume it's an action.