Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate to monorepo #1693

Closed
10 tasks done
mrook opened this issue Jan 25, 2023 · 0 comments
Closed
10 tasks done

Migrate to monorepo #1693

mrook opened this issue Jan 25, 2023 · 0 comments
Milestone
3.0.0-RC5

Comments

@mrook
Copy link
Member

mrook commented Jan 25, 2023 •
edited
Loading

The current multi-repo setup is causing more trouble than it is solving. There is a significant maintenance burden to keep individual task packages up-to-date, release new versions, and debuga/test task packages.

I've therefor made the choice to revert back to a monorepo setup, where individual task packages are published as read-only subtree splits.

Pre-migration:

Migration:

  • Add monorepo-builder dep (https://github.com/symplify/monorepo-builder)
  • Move task source files from Task/XYZ/src/ to Task/XYZ/
  • Fix namespace of SVN tasks
  • Fix composer.json
  • Add all tasks/types back to taskdef.properties / typedef.properties? Or do something with custom properties?
  • Enable on-push script
  • Make all task- repositories read only (disable issues, wiki, pull requests)
  • Update task- README files reflecting split/read-only status
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
3.0.0-RC5
Development

No branches or pull requests
1 participant
@mrook