Hi there! So, when developing a package, how do you guys manage the data flow? The key issue if, for me, that repo-based packages will use the repo root as the package root, which means that, one way or the other, you'll need to point your package sub-dir to an external repo (which is what you'll share) That approach leaves you dealing with the development project being a repo around the package repo or some such. To the Collab guys: this would be simpler if we could just set a dir when linking, so I could do "the.company.product": "https://bitbucket.org/blah/bleh.git/Package" that would allow a single Git repo to do the job. But meanwhile, what I am considering: Collab + Git: The idea is, you develop your feature in a Collab project and, at the point of publication you create a Git repo from the package subdir and push that. -pros: simple to setup -cons: Collab doesn't know about the inner Git repo, so getting the project in a different computer means then linking manually the dir with the external Git. Which can or not be trivial. Pushing to external repo won't scale. Git Modules: Develop the feature in an Unity project that's hosted in Git and then set the package dir as a submodule -pros: easy to pull and push (git sub-module update --recursive 'ish) -cons: complicated to setup, plus I don't want to fix this other guy's merge issue (or mine) inside a sub-module. Submodules require special commands for pulling/pushing. Do those approaches sound kosher enough? What do you guys use?