From d994fc95043af1f08ad2cb06432943621a8f25a8 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Wed, 17 Aug 2022 12:36:27 -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 fec751c..6f1db42 100644 --- a/gitlab/valet-migrate-lab.md +++ b/gitlab/valet-migrate-lab.md @@ -1,6 +1,6 @@ # 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. -All of the previous commands we have been using in the labs, such as `audit` and `dry-run` have been preparing us to run a migration. +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 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.