[英]Remove component specific version from bit.dev
While developing a component sometimes we push the changes to the scope (bit export) so we can import and test the changes on other projects, these versions are useless (eg: 0.0.0-test.1), so we clean them up after finishing working with the component.在开发组件时,有时我们会将更改推送到 scope(位导出),以便我们可以在其他项目上导入和测试更改,这些版本是无用的(例如:0.0.0-test.1),所以我们在之后清理它们完成与组件的工作。 We'd to have a way of cleaning those test versions using bit remove component_name --ver 1.1.0 -r
我们有办法使用 bit remove component_name --ver 1.1.0 -r 清理这些测试版本
In Bit,
you tag your new versions incrementally.在
Bit,
您以增量方式标记新版本。 That follows the Semver conventions.这遵循Semver约定。
No need to delete
older versions;无需
delete
旧版本; use the newer ones.使用较新的。 But if so you can
deprecate it
.但如果是这样,您可以
deprecate it
。 Deprecating is a nondestructive way to flag an outdated version.弃用是一种标记过时版本的非破坏性方法。
Now, that put aside, you can always open a new developing lane
.现在,抛开这些,你总能开辟一条新的发展
lane
。 A lane
is like a git branch.一个
lane
就像一个 git 分支。 It bifurcates from the original path and allows for diverging.它从原始路径分叉并允许发散。 Once you are satisfied with the diverge, you can merge it back:
一旦您对分歧感到满意,您可以将其合并回来:
bit lane merge new-feature
Conclusion: you shouldn't delete versions.结论:您不应该删除版本。 Create newer ones or depreacate.
创建更新的或弃用的。 If what you want is to diverge from the main developing line, use
bit lane
.如果你想要偏离主开发线,请使用
bit lane
。 You can always merge it back.您可以随时将其合并回来。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.