Skip to content

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

@ma2ciek

Description

@ma2ciek

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions