feat(delete), introduce --range flag to delete tags of a specific range #8844
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.
Similar to
bit deprecate --range
, this new flag allows deleting specific tags. For examplebit delete my-comp --range 0.0.1
. It marks 0.0.1 only as deleted.This is supported in
bit log
, see screenshot attached.It's also shown in the
bit import
andbit show
output. For example, when runningbit show [email protected]
the "removed" is false. However,bit show [email protected]
shows it as true. It also shows the range.Note that it'll take some time for this to be reflected on bit.cloud. It should be deployed there first.
bit log
bit show