Replies: 2 comments 1 reply
-
Hi @alpiquero , can you tell me something more about your use case? |
Beta Was this translation helpful? Give feedback.
-
Hi @alpiquero , I understand your point now but this is out of Nyx use cases. There may be workarounds (below) but introducing this in Nyx would break some foundational concepts. For example the release scope wouldn't be consistent, and this would break the whole thing. Moreover I'm wondering how it should behave when a commit affects files in more than one sub-repo or files in the project root, outside of any sub-repo. My 10 cents here, IMHO, is that this use case is somehow even outside of Git's purpose, which is instead supported by submodules. If even tagging and versioning is separate, it looks like they should be better handled as separate repos. Nonetheless, a possible (not tested) solution could be:
|
Beta Was this translation helpful? Give feedback.
-
Hi! First of all, congratulations for your awesome work. Nyx is really helping us with our repos versioning.
I would like to ask if you are planning to support monorepos in the future. I beliebe this will be useful for a lot of teams.
Beta Was this translation helpful? Give feedback.
All reactions