Add migration tooling for extracting coding-challenges to separate repository #8
+599
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The coding-challenges folder needs to be extracted into a standalone public repository at
mbianchidev/coding-challengesfor better organization and discoverability.Changes
Migration automation (
scripts/migrate-coding-challenges.sh)Documentation
MIGRATION_GUIDE.md: Three migration approaches (automated, history-preserving, manual) with troubleshootingQUICKSTART.md: One-liner execution referencecoding-challenges/README.md: Migration notice redirecting to new repositoryREADME.mdwith prominent link to new repository locationUsage
The script generates a complete repository structure ready for immediate publishing to GitHub.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.