Allow some remote actions without a bit-workspace #1837
Comments
jonisar
changed the title
bit init is required in irrelevant use cases
itaymendel
changed the title
bit init is required in irrelevant use cases
itaymendel
changed the title
davidfirst
added a commit
that referenced
this issue
Aug 1, 2019
…ce (#1884) * implements #1837, enable running "bit list" of a remote scope without a bit-workspace * allow bit-deprecate and bit-undeprecate to work outside bit-workspace * change the machine of lint to be medium instead of small (hopefully it will fix the error of "Flow returned an error: Out of retries, exiting!") * enable remove remote components using wildcards regardless whether the components exist locally * enable remove components from a remote scope outside of a bit-workspace
|
Implemented in #1884. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bit requires a local workspace to run all commands.
Some commands can be defined as 'remote only' commands and should be able to run without a workspace:
bit list <remote collection>bit show <remote component>bit remove <remote component>bit deprecate <remote component>bit undeprecate <remote component>There is no reason for these commands not to be able to work without a workspace, so there's no need to force it.
The text was updated successfully, but these errors were encountered: