How do I Move an Oxygen site to a different GitHub repo (a clone of the original)

Technical Q&A
,

Topic summary

Main issue: Migrating an existing Oxygen (Hydrogen) storefront deployment to a new GitHub organization/repository while ensuring the deployment targets the correct sales channel.

Key questions raised:

  • After cloning the repo to a new org, is it sufficient to update the GitHub Actions workflow (.github/workflows/oxygen-deployment-xxxx.yml) with:
    • SHOPIFY_HYDROGEN_DEPLOYMENT_TOKEN
    • oxygen_storefront_id
  • Should the old deployment token be deleted to prevent deployments from the original repository?

Context details: The inquiry focuses on reconfiguring deployment credentials and identifiers within the workflow to repoint the CI/CD pipeline to the appropriate storefront.

Status: No responses or confirmed steps provided yet; guidance on whether these two updates (plus revoking the old token) are sufficient remains unresolved.

Summarized with AI on December 14. AI used: gpt-5.
1

I’m leaving my present company and it has been agreed that I am taking a client with me. How do I clone the github repo into another organisation and point the github repo at the hydrogen/oxygen sales channel…

Is it just the SHOPIFY_HYDROGEN_DEPLOYMENT_TOKEN and the oxygen_storefront_id that need to be updated in the new .github/workflows/oxygen-deployment-xxxx.yml

And delete the old deployment token so that the old repo can’t push?

1 Like