[Feedhenry-raincatcher] RainCatcher Monorepo

Peter Darrow pdarrow at redhat.com
Thu Feb 23 14:21:14 UTC 2017


Hey all,

I spent a bunch of time yesterday stitching together our repos into a
single repo. My goal was to try and identify issues that might make this
challenging. You can see the results here:
https://github.com/feedhenry-raincatcher/raincatcher-stitched/. My approach
was the following:


   1. Move the demo apps into a "apps" subdirectory
   2. Move the modules into a "packages" subdirectory
   3. Move the documentation into a "docs" subdirectory
   4. Copy the branches from each individual repo to a branch on the
   monorepo with the following naming scheme: "<original branch
   name>-<original repo name>".
   5. Copy the tags from each individual repo to the monorepo with the
   following naming scheme: "<original tag name>-<original repo name>"
   6. Ensured the history stays intact.

I found a tool that promised to implement this exact approach (
http://search.cpan.org/dist/Git-FastExport/script/git-stitch-repo). It's
written in Perl and I spent an unreasonable amount of time yesterday trying
to configure my system to install CPAN modules :/. Eventually I got it
working, but if you take a look at the stitched repo, it seems to have done
an incomplete job. I'm not a Perl developer so I don't think it would be
worth my time to try to contribute a fix, but I think I could implement
something similar with a bit of effort.

What do you guys think—do we need to migrate all of the branches from each
repo, or just the master from each one? Do we care about the history? Is it
important to keep every single tag? Let me know what you think!

Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-raincatcher/attachments/20170223/de4390e0/attachment.htm>


More information about the Feedhenry-raincatcher mailing list