For various reasons we haven’t jumped on the monorepo train with our project and are using submodules for sub-components of our product. Reading the documentation it seems like submodules are not yet supported.
In order to associate issues fixed in submodules with Linear releases I think we’d need an option to have linear-release recurse into submodules to detect Linear issue references.
With this setup, linear-release would still only be called from the main (root) repo, and a release would still only be associated with a commit SHA from the main repo (as the submodule pointers are taken from that state of the main repo).
Your support suggested to manually scan the submodules in addition to the main repo, but I don’t think this would work for continuous pipelines, where every deployment creates a completed release. Also for scheduled pipelines it is unclear to me if a release can be associated with multiple repositories.
For various reasons we haven’t jumped on the monorepo train with our project and are using submodules for sub-components of our product. Reading the documentation it seems like submodules are not yet supported.
In order to associate issues fixed in submodules with Linear releases I think we’d need an option to have linear-release recurse into submodules to detect Linear issue references.
With this setup, linear-release would still only be called from the main (root) repo, and a release would still only be associated with a commit SHA from the main repo (as the submodule pointers are taken from that state of the main repo).
Your support suggested to manually scan the submodules in addition to the main repo, but I don’t think this would work for continuous pipelines, where every deployment creates a completed release. Also for scheduled pipelines it is unclear to me if a release can be associated with multiple repositories.