Skip to content

Merge several subrepos into bundle repo (monorepoify) #227

@ErikBjare

Description

@ErikBjare

Right now I'm really bothered by the overhead of managing submodules, CI, and releases. Things would be a lot simpler if a lot of things were brought into one repo.

Then I read this: https://danluu.com/monorepo/

Has been discussed a little before in: #70

Things that would improve:

  • Most issues would go in the standard activitywatch repo (easier overview, less cross-referencing)
  • Open PRs would become easier to overview and cross-repo changes could be put in a single PR instead of spread across repos
  • CI would be easier to maintain and run full integration tests on all projects for every commit
  • Easier to install

Things that would worsen:

  • CI build times
  • The contributor stats stuff would have to be rewritten

Repos I'd merge in:

  • aw-core
  • aw-server
  • aw-webui
  • aw-client
  • aw-client-js
  • aw-watcher-afk
  • aw-watcher-window
  • aw-watcher-web

Things we'd have to do:

  • For each repo to be merged:
    • In original repo, check out a new branch, move all files into subfolder with same name as repo, commit.
    • In destination repo, git merge the original repo's pre-merge branch.
  • Move all issues and open PRs

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