ee-migrate now writes a GitHub Actions workflow that builds and deploys your site
TL;DR: ee-cdn-cli 0.6.0's ee-migrate turns the build settings in netlify.toml into a GitHub Actions workflow. It builds your site the way Netlify did and deploys it on every push. Variables that look like credentials are read from repository secrets.
When you move a site from Netlify, the build that ran on every push has to move too. ee-migrate already carries over your netlify.toml redirects and headers. Now it also turns the file’s build settings into a GitHub Actions workflow that builds your site the way Netlify did for production deploys and deploys it to Evolving Edge on every push. You don’t have to write the workflow yourself.
npx --package=@evolving-edge/ee-cdn-cli ee-migrate ./my-site
What it writes
.github/workflows/ee-deploy.yml, at the root of your git repository. It runs your build command in yourbasefolder and deploys thepublishfolder with the Deploy to Evolving Edge CDN Action (evolving-edge/deploy-action@v1).- It uses your production settings. Values in
[context.production]take precedence over[build], as they did on Netlify. - It runs on every push to your default branch, and you can also start it by hand. It only reads your repository and runs one deploy at a time.
- Your domain, project and token are read from the repository variables
EE_CDN_DOMAINandEE_CDN_PROJECT_IDand the secretEE_CDN_TOKEN. The summary prints theghcommands that create them. To write the domain and project into the workflow instead, pass--domainand--project.
Toolchains
- Node and Hugo are set up for you. Node uses the version your site names, from
NODE_VERSION,.nvmrc,.node-versionorengines.node, or 22 if none is set; the summary says which. Dependencies are installed with the package manager that matches your lockfile. - Any other tool your build needs, such as make, Python, Ruby or Go, is named in the summary and marked in the workflow where you add its install steps.
Build variables that look like credentials
- They’re read from repository secrets, given only to the install and build steps. A variable counts as one when its name contains
TOKEN,KEY,SECRET,PASSWORDorAUTH, or its value looks like a known kind of credential. - Rotate them. They’re committed in
netlify.toml, so the summary tells you to replace them. - The rule matches parts of names, so a variable like
NEXTAUTH_URLorSITE_AUTHORbecomes a secret too. Pass--plain <NAME>to keep one as an ordinary variable, or--secret <NAME>to make one a secret. Both can be given more than once. - Values are never printed or written into the report or the workflow. Netlify’s own settings are left out of the workflow.
Your own workflow is safe
An ee-deploy.yml that ee-migrate didn’t write, wrote for another site, or that you’ve edited since is never replaced. The run stops before writing anything, including _redirects and _headers. Pass --workflow <path> to write it somewhere else, or --no-workflow to skip it.
New options
--no-workflow: don’t write the workflow.--workflow <path>: write it somewhere else.--domainand--project: write these values into the workflow instead of reading repository variables.--secret <NAME>and--plain <NAME>: decide how one build variable is handled.
Limits
- It needs an ee-builder that includes the deploy workflow. With an older one, no workflow is written and
ee-migratesays so; your redirects and headers are carried over as before. The other workflow options stop the run, naming the ones that ee-builder can’t take. - Only Node and Hugo are installed for you. Other tools need their install steps added by hand.
- The workflow has been tested step by step, but not yet on GitHub’s own runners, so check the log of its first run.
What you need to do
Nothing, unless you’re moving a site from Netlify. If you are, run ee-migrate on the site’s folder, create the variables and secrets the summary lists, rotate any credentials it names, and commit the workflow. If you deploy some other way, pass --no-workflow.