-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove recursive and other changes. #711
Remove recursive and other changes. #711
Conversation
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-17 17:25:29 UTC |
3c4d140
to
679faca
Compare
cli/popper/commands/cmd_run.py
Outdated
|
||
1. When no TARGET argument is passed, Popper will search for the | ||
When no action argument is passed, Popper will search for the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should read:
By default, Popper searches for a workflow in
.github/main.workflow
or./main.workflow
and it executes it if found.
b366601
to
ed0bbe3
Compare
ed0bbe3
to
6f795a5
Compare
running workflows recursively is now only done when CI=true is defined
running workflows recursively is now only done when CI=true is defined
running workflows recursively is now only done when CI=true is defined
running workflows recursively is now only done when CI=true is defined
running workflows recursively is now only done when CI=true is defined
Remove
--recursive
option for Popper CLI