Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use bit show --remote to get aspect version #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

itaymendel
Copy link
Contributor

You can use the bit show teambit.angular/angular-v12 --remote command syntax to get the latest version of any aspect (also - bit list teambit.angular --remote to see versions for all aspects in a scope).

You can use the `bit show teambit.angular/angular-v12 --remote` command syntax to get the latest version of any aspect (also - `bit list teambit.angular --remote` to see versions for all aspects in a scope).
@itaymendel
Copy link
Contributor Author

@ocombe
if the output is too verbose (as it gives a very complete information on the aspect), it's likely we'll want to add an option to only print the version before this is merged, to improve dev-ex.

@itaymendel itaymendel requested a review from ocombe July 4, 2021 08:09
@ocombe
Copy link
Member

ocombe commented Jul 4, 2021

it's very verbose, and it takes a very long time, while the npm command is super fast and gives just what we need, I don't think we should change that for now 🙂

@itaymendel
Copy link
Contributor Author

let's keep it open and add @davidfirst and @GiladShoham to the mix.
ideally id' like to use the same tool for all commands. so for now we can keep npm, but i would want to replace with bit. need to see about our options.

@davidfirst
Copy link
Member

I'm good either way. It'd be nice to add an option to show only the remote version. Agree that it's too verbose. On my local it's not that slow, it takes 3 seconds.

@ocombe ocombe force-pushed the master branch 2 times, most recently from 7bc536d to c32299a Compare July 13, 2021 18:27
@GiladShoham
Copy link
Member

@davidfirst We already have the _latest command, we can expose it as a public command and use it instead.

@davidfirst
Copy link
Member

@GiladShoham , yes, we can do it. It'll probably require some work as it'll need to be implemented for HTTP.

@ocombe ocombe force-pushed the master branch 12 times, most recently from fedcf1d to afab0f3 Compare July 27, 2021 06:40
@ocombe ocombe force-pushed the master branch 2 times, most recently from 264dc0a to fbd7d05 Compare August 9, 2021 14:12
@ocombe ocombe force-pushed the master branch 2 times, most recently from de86f0a to ce28839 Compare October 7, 2021 11:47
@ocombe ocombe force-pushed the master branch 2 times, most recently from 1c1e1a8 to 436ddbf Compare November 23, 2021 15:24
@ocombe ocombe force-pushed the master branch 3 times, most recently from 3bfef81 to e3b69c3 Compare March 3, 2023 16:27
@ocombe ocombe force-pushed the master branch 4 times, most recently from a0a191f to a70ce0d Compare May 9, 2023 14:26
@ocombe ocombe force-pushed the master branch 2 times, most recently from 13543e5 to 2d0f1ac Compare July 28, 2023 16:45
@ocombe ocombe force-pushed the master branch 4 times, most recently from 1b600ea to e94ecec Compare September 29, 2023 13:24
@ocombe ocombe force-pushed the master branch 8 times, most recently from d61ca39 to b818021 Compare October 16, 2023 09:29
@ocombe ocombe force-pushed the master branch 2 times, most recently from febca6f to ecd68a1 Compare October 19, 2023 14:24
@ocombe ocombe force-pushed the master branch 3 times, most recently from d5c0894 to a0065ca Compare December 1, 2023 15:03
@ocombe ocombe force-pushed the master branch 2 times, most recently from 591f66a to b0a0d44 Compare February 5, 2024 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants