Skip to content

Better tooling for using multirepos #70

@ErikBjare

Description

@ErikBjare

So, I've been thinking a bunch about our multirepo strategy and its gone pretty back and forth.

My thoughts so far:

  • Multirepos lead to clearer dependencies/modules/separation of concerns
  • You can pretty easily (and cleanly) go from a multirepo to a monorepo. The other way isn't so easy.
  • One downside is the increased overhead required (updating submodules in the bundle repo, having to merge multiple inter-dependent PRs from time to time). Not much to do about this that I can see, I think the benefits are worth it so far.
  • Lack of good tooling: many are embracing monorepos at large scales (Facebook, Chromium) and that leads to less investment in multirepo tooling.

Tooling to develop:

  • Tool to get collect contributor stats across multiple repos (Done! See contributor-stats)
  • Tool that generates diffs and/or get a list of added commits (and their messages) in submodules between bundle-repo commits. This would help greatly with making changelogs.

This is just some thoughts I wanted to get out there, I think the multirepo/monorepo discussion is an interesting configuration management issue and I definitely want to learn more.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions