All commands should be executable no-interactively #13
Labels
Comments
|
@dantleech do you also mean to make core:configure non-interactive?
|
|
@dantleech , i believe we can do interactive all of the commands but the core:configure since the adapter has a doConfigure method to which only dialog and output is passed but not input, and also it would not have the custom options that an adapter may have or not. Any ideas? or is that ok to leave configure out of the equation. |
cordoval
added a commit
that referenced
this issue
Mar 14, 2014
…able-no-interactively
This PR was merged into gushphp:master branch.
Discussion
----------
added no-interaction to all commands but core:configure
|Q |A |
|--- |---|
|Bug Fix? |n |
|New Feature? |n |
|BC Breaks? |n |
|Deprecations?|n |
|Tests Pass? |n |
|Fixed Tickets|#13|
|License |MIT|
|Doc PR | |
added no-interaction to fork command test
Commits
-------
dc052f0 adding no-interaction to fork command tests cslucano
a8d71e1 added no interactive to configure command cslucano
95dd99c added no interactive to issue command cslucano
944a6fc added no interactive on pull request test cslucano
7325793 added options to issue create and label command to skip interactive cslucano
09cb1c9 added issue body option to issue create command cslucano
378ff68 added test to issue create command with options cslucano
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
imported from https://github.com/cordoval/gush/issues/146
All commands should be executable non-interactively with options
The text was updated successfully, but these errors were encountered: