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.

Sign up for GitHub

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

Jump to bottom

mgit st might log, that the package in the packages is not listed in mgit.json #64

Open
ma2ciek opened this issue Nov 29, 2017 · 1 comment
Open

mgit st might log, that the package in the packages is not listed in mgit.json #64

ma2ciek opened this issue Nov 29, 2017 · 1 comment
Labels
type:feature

Comments

@ma2ciek
Copy link
Contributor

ma2ciek commented Nov 29, 2017

Let's assume that we're developing some package and clone it directly to the packages directory.
Now when running npm run test in CKE5, this package will be tested. But mgit st won't show that something is wrong.

PS: I'm not sure whether this should be done on the mgit side or the CKE5 side.
@pomek
Copy link
Member

pomek commented Mar 27, 2018

mgit st could print a warning below the table if a number of packages cloned into the packages/ directory are other than specified in mgit.json.

@Reinmar Reinmar added this to the next milestone Jan 11, 2019
@pomek pomek removed this from the nice-to-have milestone Feb 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Reinmar @pomek @ma2ciek @mlewand