Repository navigation
build: drop the no-op --release flag - #91
Merged
Merged
Conversation
Releasing is `comline release` now; a reserved `build --release` next to it only invites confusion. The build help also stops saying each build bumps the version: a build is recorded under a pre-release version.
This file contains hidden or 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
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.
comline build --releasewas reserved and did nothing. Now that releasing iscomline release(#90), the flag only invites confusion, so it goes before anyone relies on it.comline build.0.3.0-dev.2), andcomline releasemakes the release.Docs: ComlineProject/docs#72, whose CLI drift check needs this merged first.