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
We enjoy moon as a tool to manage very large multi-module projects, but we still have use cases where it is desirable to have a couple of these repos rather than a single large one. In which case, we find certain moon tasks common across our repositories, so being able to extend from a common config is very desirable.
For users that will write custom tasks that don't make sense outside of their use cases, what are recommended strategies for sharing those configs? The examples from the moon docs only demonstrates public github user content which wouldn't work if we wanted to keep the custom tasks private.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am excited for this feature: https://moonrepo.dev/docs/guides/sharing-config
We enjoy moon as a tool to manage very large multi-module projects, but we still have use cases where it is desirable to have a couple of these repos rather than a single large one. In which case, we find certain moon tasks common across our repositories, so being able to extend from a common config is very desirable.
For users that will write custom tasks that don't make sense outside of their use cases, what are recommended strategies for sharing those configs? The examples from the moon docs only demonstrates public github user content which wouldn't work if we wanted to keep the custom tasks private.
Beta Was this translation helpful? Give feedback.
All reactions