Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / lerna/lerna issues and pull requests
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2808 - Having a remote named something other than 'origin' breaks `lerna publish`
Issue -
State: closed - Opened by ELLIOTTCABLE about 4 years ago
- 14 comments
#2787 - LERNA_ROOT_PATH seems not working with node v15.5.0
Issue -
State: closed - Opened by RoCat about 4 years ago
- 3 comments
#2787 - LERNA_ROOT_PATH seems not working with node v15.5.0
Issue -
State: closed - Opened by RoCat about 4 years ago
- 3 comments
#2787 - LERNA_ROOT_PATH seems not working with node v15.5.0
Issue -
State: closed - Opened by RoCat about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2761 - [Suggestion] Initial release 0.x.y to 1.0.0 in an automated CI release
Issue -
State: open - Opened by matzeeable about 4 years ago
- 3 comments
#2760 - feat(version): support custom command for git tag
Pull Request -
State: closed - Opened by evangelion1204 about 4 years ago
- 10 comments
#2760 - feat(version): support custom command for git tag
Pull Request -
State: closed - Opened by evangelion1204 about 4 years ago
- 10 comments
#2760 - feat(version): support custom command for git tag
Pull Request -
State: closed - Opened by evangelion1204 about 4 years ago
- 10 comments
#2760 - feat(version): support custom command for git tag
Pull Request -
State: closed - Opened by evangelion1204 about 4 years ago
- 10 comments
#2760 - feat(version): support custom command for git tag
Pull Request -
State: closed - Opened by evangelion1204 about 4 years ago
- 10 comments
#2760 - feat(version): support custom command for git tag
Pull Request -
State: closed - Opened by evangelion1204 about 4 years ago
- 10 comments
#2760 - feat(version): support custom command for git tag
Pull Request -
State: closed - Opened by evangelion1204 about 4 years ago
- 10 comments
#2760 - feat(version): support custom command for git tag
Pull Request -
State: closed - Opened by evangelion1204 about 4 years ago
- 10 comments
#2760 - feat(version): support custom command for git tag
Pull Request -
State: closed - Opened by evangelion1204 about 4 years ago
- 10 comments
#2760 - feat(version): support custom command for git tag
Pull Request -
State: closed - Opened by evangelion1204 about 4 years ago
- 10 comments
#2760 - feat(version): support custom command for git tag
Pull Request -
State: closed - Opened by evangelion1204 about 4 years ago
- 10 comments
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 27 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 26 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 26 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2730 - `lerna publish` unable to authenticate with Artifactory
Issue -
State: open - Opened by lauraglasu over 4 years ago
- 25 comments
Labels: type: bug
#2727 - [Question]: Can I pass command to lerna version to put current date into package.json?
Issue -
State: closed - Opened by acidiney over 4 years ago
- 2 comments
Labels: stale
#2727 - [Question]: Can I pass command to lerna version to put current date into package.json?
Issue -
State: closed - Opened by acidiney over 4 years ago
- 2 comments
Labels: stale
#2711 - Do not use red color in console output
Issue -
State: open - Opened by otakustay over 4 years ago
- 2 comments
#2703 - Lerna is largely unmaintained
Issue -
State: closed - Opened by MikeActually over 4 years ago
- 105 comments
#2703 - Lerna is largely unmaintained
Issue -
State: closed - Opened by MikeActually over 4 years ago
- 105 comments
#2703 - Lerna is largely unmaintained
Issue -
State: closed - Opened by MikeActually over 4 years ago
- 105 comments
#2703 - Lerna is largely unmaintained
Issue -
State: closed - Opened by MikeActually over 4 years ago
- 105 comments
#2703 - Lerna is largely unmaintained
Issue -
State: closed - Opened by MikeActually over 4 years ago
- 105 comments
#2703 - Lerna is largely unmaintained
Issue -
State: closed - Opened by MikeActually over 4 years ago
- 105 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments
#2668 - Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"
Issue -
State: open - Opened by alexforsyth over 4 years ago
- 20 comments