Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 15 commits
- 17 files changed
- 10 contributors
Commits on Jun 19, 2017
Commits on Jun 23, 2017
Commits on Jun 24, 2017
Commits on Jun 26, 2017
-
Support setting name in #name function and make it chainable
Similar to #description, #name now behaves like a setter when given an argument, and like a setter otherwise.
Commits on Jun 27, 2017
-
-
Since old nodejs are no longer supported
-
-
Commits on Jun 29, 2017
Commits on Jul 3, 2017
-
feature: support for signals to subcommands (#632)
* add basic subcommand signal tests and fixture These tests verify that a signal sent to the process is correctly propagated to the subcommand * add propagation of supported signals to subcommands Choice of supported signals: https://nodejs.org/api/process.html#process_signal_events * increase timeout for subcommand signal handling for better success rate * increase timeout for subcommand spawn for better success rate in tests * make pm-listen fixture executable * finetune SIGUSR1 test for possible warning from node
-
Fix help section order and padding (#652)
* Change help section order Fixes #500 Previous display order : Usage > Commands > Description > Options New display order: Usage > Description > Options > Commands * Fix inconsistent padding between help sections
-
* version bump 2.11.0 * Add line feed for format unification
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2.10.0...v2.11.0