Standardize skipping and enabling tasks #566
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Most flags completely disable the task when explicitly specified (for example, `--no-cleanup` or `--no-tests` but also `--yolo`). This commit standardizes that behavior across all tasks. See sindresorhus#513 (comment).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Standardizes the behavior of skipping and enabling tasks as discussed in #513 (comment).
Apart from preview mode, there are now only two remaining cases where a task is skipped: “Pushing tags” when there’s no upstream branch (source) and when publishing failed (source). While the latter is certainly fine and expected, the former may be worthy of discussion. After all, the user may intentionally not have an upstream branch. For comparison,
npalso doesn’t skip “Running tests using npm” when there’s notestscript.Closes #513.