fix: Migration script should also work for repos configured as "forks" #205
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the migration script to handle enterprise repositories configured as "forks" that don't have an "origin" remote. Previously, the script assumed all repos had an "origin" remote, which caused failures for fork repos configured with "edx" and "openedx" remotes instead.
- Adds conditional logic to detect whether a repo uses "origin" or fork-based remote configuration
- For fork repos, updates the main/master branch tracking remote from "openedx" to "edx"
- Changes debug settings to enable command tracing
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
pwnage101
force-pushed
the
pwnage101/fix-migration-script-x2
branch
2 times, most recently
from
6c2be9a to
3a4ad97
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
pwnage101
force-pushed
the
pwnage101/fix-migration-script-x2
branch
2 times, most recently
from
d17005b to
14aa29b
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Previously, I had assumed all repos had an "origin" remote. This is a fatal assumption because several enterprise repos had been included in FORKED_REPOS on newer devstacks so they were configured without an "origin" remote. This fixes the migration script to handle the fork repo case---instead of re-writing the "origin" remote, re-point the main branch to track the "edx" remote instead of the "openedx" remote. ENT-11240 (epic: ENT-11239)
pwnage101
force-pushed
the
pwnage101/fix-migration-script-x2
branch
from
14aa29b to
ecd16b9
Compare
Previously, I had assumed all repos had an "origin" remote. This is a fatal assumption because several enterprise repos had been included in FORKED_REPOS on newer devstacks so they were configured without an "origin" remote. This fixes the migration script to handle the fork repo case---instead of re-writing the "origin" remote, re-point the main branch to track the "edx" remote instead of the "openedx" remote.
ENT-11240 (epic: ENT-11239)
Testing
From devstack:
That resulted in all 4 enterprise IDA checkouts to have their main/master branches re-target the "edx" remote. Re-running the command is idempotent: