From db0d5673c1a4e26a6f239583e969bf21123b7a48 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Wed, 17 Aug 2022 12:37:09 -0400 Subject: [PATCH] Update gitlab/valet-migrate-lab.md Co-authored-by: Begona Guereca --- gitlab/valet-migrate-lab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gitlab/valet-migrate-lab.md b/gitlab/valet-migrate-lab.md index 6f1db42..1116f6a 100644 --- a/gitlab/valet-migrate-lab.md +++ b/gitlab/valet-migrate-lab.md @@ -1,7 +1,7 @@ # Migrate an GitLab Project to GitHub Actions In this lab, we will use the Valet `migrate` command to migrate a GitLab pipeline to GitHub Actions. The previous commands used in the labs, such as `audit` and `dry-run` have prepared us to run a migration. -The `migrate` command will generate the GitHub Actions workflow files, like the `dry-run` did, and additionally create a pull request with the files. +The `migrate` command will transform the Gitlab pipeline into a GitHub Actions workflow like the `dry-run` command did, but instead of writing these files locally, it will open a pull request with the files. The pull request will also contain a checklist of `Manual Tasks` if required. These tasks are changes that Valet could not do on our behalf, like creating a runner or adding a secret to a repository. - [Prerequisites](#prerequisites)