You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once a library has been migrated into the core monorepo, its original repo is archived and sunsetted. Before that happens, we want to preserve the issues and PRs that are in the original repo by transferring them into the monorepo.
We will explore and compare solutions (e.g. bash script, third-party tool, GitHub API or gh) for fetching the issues and pull requests and recreating them on the monorepo.
Requirements
The solution must be easily reusable for any library migration.
We may want to ensure that there's some indication for future readers (e.g. prefix, non-user author) that the transferred issues/PRs were copied from another repo.
Following discussion with @mcmire@Gudahtt, we'll be opting against recreating all of the source repo's issues/PRs/branches in core.
The archived source repo is sufficient for historic preservation purposes.
Open issues: move to core manually using the Transfer issue feature.
Open PRs: ask author to re-open PR in core, and add link to the original PR for context on the previous discussion.
Possibly investigate in new ticket: Recreate open PRs in core using the migration tool, and instruct original author to add new commits to the recreated branches.
Explanation
Once a library has been migrated into the core monorepo, its original repo is archived and sunsetted. Before that happens, we want to preserve the issues and PRs that are in the original repo by transferring them into the monorepo.
We will explore and compare solutions (e.g. bash script, third-party tool, GitHub API or
gh
) for fetching the issues and pull requests and recreating them on the monorepo.Requirements
Resources
The text was updated successfully, but these errors were encountered: