Skip to content

Migration doc fixes #4

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

Merged
jayhawk-commits merged 3 commits into from
Apr 7, 2025
Merged

Migration doc fixes #4

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4c3f2ee
Initial migration document draft
jayhawk-commits Apr 7, 2025
6c1861a
Update migration.md
jayhawk-commits Apr 7, 2025
276ddb3
Merge branch 'develop' into joseph/migrationDoc
jayhawk-commits Apr 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,9 +41,6 @@ The projects in scope will be imported into the monorepo under a dedicated subdi

Continue using the current branching models.

Automatic updates from the monorepo to these repositories is disabled in the beginning.
Updates must be done manually through `git subtree push` commands.

### Monorepo

Use trunk-based development:
Expand Down Expand Up @@ -119,7 +116,7 @@ Updates from this monorepo to the individual legacy repositories must be done ma
- Monorepo CI and build tools
- Maintain channels for questions, feedback, and issue reporting

11. Known Limitations and Risks
## Known Limitations and Risks

- Subtree operations are slower on large histories
- Cannot do shallow clones or partial history fetches with git subtree
Expand Down