actions/importer-labs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update 2-audit.md

Browse Source
This commit is contained in:
j-dunham
2022-09-06 10:40:26 -04:00
committed by GitHub
parent 08f0a353e3
commit 94b5c6bec3
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
gitlab/2-audit.md
+3 -3
View File
@@ -304,7 +304,7 @@ Unsupported: **1 (0%)**
- artifacts.terraform: **1**
```
Under the `Actions` section in `Build Steps` we have the list of the Actions that were used in order to implement the transformation of all of these build steps.
Under the `Actions` section in `Build Steps` we have the list of the Actions that were used in order to implement the transformation of the of the `known` build steps.
```yaml
Actions: **135**
@@ -322,8 +322,8 @@ Actions: **135**
Valet is a planning tool that can help in facilitating the migration into GitHub Actions and this list of Actions is a great place to understand what dependencies you would be taking on third-party Actions after this migration. For example, if you are doing things like setting up the allow list of third-party Actions in a GitHub Enterprise server instance this list of Actions is a fantastic place to begin security reviews and audits of what third-party actions to depend on.
Valet breaks down the pipeline components further into `Triggers`, `Environment`, `Other`, and `Manual tasks`.
- Triggers are a list of pipeline trigger found
- Environment are a list of project variables found
- Triggers are a list of pipeline trigger found.
- Environment are a list of project variables found.
- Manual tasks are a list of user tasks that needs to be done in order for a pipeline to be functional when migrating to GitHub, such as adding `secrets` for a masked project variable, like we see here for the variable `PASSWORD`. In a later lab we will see how these manual tasks appear on a pull request when we do a migration.
```
Secrets: **1**