You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
publish to publish, optional org, optional org/package, handles bumping versions
link <org> links together an orgs files (multiple orgs?)
exec -- npm run watch good, but what about if some dont have watch? watch maybe?
cd helps you cd into things, preferably with fuzzy match repoman cd chunky
Major questions:
Linking into monorepo requires some sort of knowledge of the monorepo and all its sub-packages which is an unfortunate complexity... any way to simplify???
link <...orgs> --into mono-repo --recursive could do it
Finally, not sure why we have dependencies key in config, that should be handled flexibly without needing a config.
Questions on having a repos(.json)? inside ~/projects/*:
Can share with team to have consistent dev env
Where do you store it? Github?
Perhaps it could just point to a remote file! the whole file could just be:
motion/repos/repos.json
then on clone it could pull everything from that?.... (complex)
How do you keep things in sync?
repoman clone-set []
repoman clone motion/repos/repos.json smart?
repoman new set => prompts for location
Naming for "sets" or "groups" or "orgs":
repoman sets => show list of sets?
repoman set clone [] => commands for a set? but this is weird...
repoman clone set [] => better
repoman set motion publish => prefix with set?
repoman publish motion => or postfix? seems less flexible
The text was updated successfully, but these errors were encountered:
publish
to publish, optional org, optional org/package, handles bumping versionslink <org>
links together an orgs files (multiple orgs?)exec -- npm run watch
good, but what about if some dont have watch?watch
maybe?cd
helps you cd into things, preferably with fuzzy matchrepoman cd chunky
Major questions:
Linking into monorepo requires some sort of knowledge of the monorepo and all its sub-packages which is an unfortunate complexity... any way to simplify???
link <...orgs> --into mono-repo --recursive
could do itFinally, not sure why we have
dependencies
key in config, that should be handled flexibly without needing a config.Questions on having a
repos(.json)?
inside~/projects/*
:motion/repos/repos.json
clone
it could pull everything from that?.... (complex)repoman clone-set []
repoman clone motion/repos/repos.json
smart?repoman new set
=> prompts for locationNaming for "sets" or "groups" or "orgs":
repoman sets
=> show list of sets?repoman set clone []
=> commands for a set? but this is weird...repoman clone set []
=> betterrepoman set motion publish
=> prefix with set?repoman publish motion
=> or postfix? seems less flexibleThe text was updated successfully, but these errors were encountered: