Skip to content

Prototype monorepo architecture #823

Closed
Closed
Prototype monorepo architecture#823
Assignees
mcmire

Description

@mcmire
mcmire
opened on May 11, 2022

The way we maintain controllers currently will change when we convert it to a monorepo, and we need to work out those changes. I'm going to research this by making another repo, privately, where I can experiment with some ideas and work out some processes. I'll post my learnings as I go along.

Activity

  1. mcmire
    self-assigned this
    on May 11, 2022

  2. mcmire commented on May 19, 2022

    @mcmire
    mcmire
    on May 19, 2022
    CollaboratorAuthor

    I've made a PR where I talk about some of the things I found and offer some possible solutions: #831. The goal wasn't to finish the prototype but merely start it, so this is complete.

  3. mcmire
    closed this as completedon May 19, 2022
  4. mcmire
    reopened this on May 19, 2022

  5. Gudahtt commented on Jun 30, 2022

    @Gudahtt
    Gudahtt
    on Jun 30, 2022
    Member

    This is basically done, but leaving this open until we have a summary of the results written down somewhere.

  6. Gudahtt commented on Jul 28, 2022

    @Gudahtt
    Gudahtt
    on Jul 28, 2022
    Member

    Closed by https://www.notion.so/Core-Monorepo-Release-Automation-a65b28ab89a14c9d82dcf9fabc3eb1e1

  7. Gudahtt
    closed this as completedon Jul 28, 2022
  8. MoMannn
    added a parent issue on Jun 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions