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

Merge pull request #39 from actions/update-for-ga

Browse Source 
Remove references to public preview
This commit is contained in:
Ethan Dennis
2023-03-01 07:29:10 -08:00
committed by GitHub
parent 49b9740a60 c1a7803b17
commit d749e6a7ae
8 changed files with 10 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
LICENSE
+1 -1
View File
@@ -1,6 +1,6 @@
MIT License
Copyright (c) 2022 GitHub
Copyright (c) 2023 GitHub
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
azure_devops/1-configure.md
+1 -5
View File
@@ -32,7 +32,7 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
- Click `Personal access tokens` and then `Tokens (classic)` (if present).
- Click `Generate new token` and then `Generate new token (classic)`. You may be required to authenticate with GitHub during this step.
- Name your token in the `Note` field.
- Select the following scopes: `workflow` and `read:packages`.
- Select the following scope: `workflow`.
- Click `Generate token`.
- Copy the generated PAT and save it in a safe location.
@@ -40,8 +40,6 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
- Select the `TERMINAL` tab from within the codespace terminal.
- Run the following command: `gh actions-importer configure`.
- Use the down arrow key to highlight `Azure DevOps`, press the spacebar to select, and then press enter to continue.
- At the GitHub handle prompt, enter the GitHub handle used to generate the GitHub PAT in step 2 and press enter.
- At the GitHub Container Registry prompt, enter the GitHub PAT generated in step 2 and press enter.
- At the GitHub PAT prompt, enter the GitHub PAT generated in step 2 and press enter.
- At the GitHub URL prompt, enter the GitHub instance URL or press enter to accept the default value (`https://github.com`).
- At the Azure DevOps token prompt, enter the access token from step 1 and press enter.
@@ -53,8 +51,6 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
$ gh actions-importer configure
✔ Which CI providers are you configuring?: Azure DevOps
Enter the following values (leave empty to omit):
✔ GitHub handle used to authenticate with the GitHub Container Registry: mona
✔ Personal access token to authenticate with the GitHub Container Registry: ***************
✔ Personal access token for GitHub: ***************
✔ Base url of the GitHub instance: https://github.com
✔ Personal access token for Azure DevOps: ***************
circle_ci/1-configure.md
+1 -5
View File
@@ -12,7 +12,7 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
- In the left panel, click `Developer Settings`.
- Click `Personal access tokens` and then `Tokens (classic)` (if present).
- Click `Generate new token` and then `Generate new token (classic)`. You may be required to authenticate with GitHub during this step.
- Select the following scopes: `read:packages` and `workflow`.
- Select the following scope: `workflow`.
- Click `Generate token`.
- Copy the generated PAT and save in a safe location.
@@ -22,8 +22,6 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
- Select the `TERMINAL` tab from within the codespace terminal window.
- Run the following command: `gh actions-importer configure`.
- Using the down arrow key to highlight `CircleCI`, press the spacebar to select, and then press enter to continue.
- At the GitHub handle prompt, enter the GitHub username used to generate the GitHub PAT in step 2 and press enter.
- At the GitHub Container Registry prompt, enter the GitHub PAT generated in step 1 and press enter.
- At the GitHub PAT prompt, enter the GitHub PAT generated in step 1 and press enter.
- At the GitHub URL prompt, enter the GitHub instance URL or press enter to accept the default value (`https://github.com`).
- At the CircleCI token prompt, enter the CircleCI access token from step 2 and press enter.
@@ -34,8 +32,6 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
$ gh actions-importer configure
✔ Which CI providers are you configuring?: CircleCI
Enter the following values (leave empty to omit):
✔ GitHub handle used to authenticate with the GitHub Container Registry: mona
✔ Personal access token to authenticate with the GitHub Container Registry: ***************
✔ Personal access token for GitHub: ***************
✔ Base url of the GitHub instance: https://github.com
✔ Personal access token for CircleCI: ***************
contributing.md
+2 -2
View File
@@ -8,6 +8,6 @@ Please note that this project is released with a [Contributor Code of Conduct](c
Here's some helpful notes on how to contribute to this project, including details on how to get started working with the codebase.
## How to submit a bug or request a feature
## How to offer feedback or make a feature request
If you think you've found a bug or have a great idea for new functionality please create an issue in the [repo](https://github.com/actions/importer-labs/issues/new).
If you would like to offer feedback or have a great idea for new functionality, please create a new discussion [here](https://github.com/actions/importer-labs/discussions/new/choose).
gitlab/1-configure.md
+1 -5
View File
@@ -32,7 +32,7 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
- Click `Personal access tokens` and then `Tokens (classic)` (if present).
- Click `Generate new token` and then `Generate new token (classic)`. You may be required to authenticate with GitHub during this step.
- Name your token in the `Note` field.
- Select the following scopes: `workflow` and `read:packages`.
- Select the following scope: `workflow`.
- Click `Generate token`.
- Copy the generated PAT and save it in a safe location.
@@ -40,8 +40,6 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
- Select the `TERMINAL` tab from within the codespace terminal window.
- Run the following command: `gh actions-importer configure`.
- Use the down arrow key to highlight `GitLab`, press the spacebar to select, and then press enter to continue.
- At the GitHub handle prompt, enter the GitHub handle used to generate the GitHub PAT in step 2 and press enter.
- At the GitHub Container Registry prompt, enter the GitHub PAT generated in step 4 and press enter.
- At the GitHub PAT prompt, enter the GitHub PAT generated in step 4 and press enter.
- At the GitHub URL prompt, enter the GitHub instance URL or press enter to accept the default value (`https://github.com`).
- At the GitLab token prompt, enter the GitLab access token from step 3 and press enter.
@@ -51,8 +49,6 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
$ gh actions-importer configure
✔ Which CI providers are you configuring?: GitLab
Enter the following values (leave empty to omit):
✔ GitHub handle used to authenticate with the GitHub Container Registry: mona
✔ Personal access token to authenticate with the GitHub Container Registry: ***************
✔ Personal access token for GitHub: ***************
✔ Base url of the GitHub instance: https://github.com
✔ Private token for GitLab: ***************
jenkins/1-configure.md
+1 -5
View File
@@ -26,7 +26,7 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
- Click `Personal access tokens` and then `Tokens (classic)` (if present).
- Click `Generate new token` and then `Generate new token (classic)`. You may be required to authenticate with GitHub during this step.
- Name your token in the `Note` field.
- Select the following scopes: `workflow` and `read:packages`.
- Select the following scope: `workflow`.
- Click `Generate token`.
- Copy the generated PAT and save it in a safe location.
@@ -34,8 +34,6 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
- Select the `TERMINAL` tab from within the codespace terminal window.
- Run the following command: `gh actions-importer configure`.
- Use the down arrow key to highlight `Jenkins`, press the spacebar to select, and then press enter to continue.
- At the GitHub handle prompt, enter the GitHub username used to generate the GitHub PAT in step 3 and press enter.
- At the GitHub Container Registry prompt, enter the GitHub PAT generated in step 3 and press enter.
- At the GitHub PAT prompt, enter the GitHub PAT generated in step 3 and press enter.
- At the GitHub URL prompt, enter the GitHub instance URL or press enter to accept the default value (`https://github.com`).
- At the Jenkins token prompt, enter the Jenkins access token from step 2 and press enter.
@@ -46,8 +44,6 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
$ gh actions-importer configure
✔ Which CI providers are you configuring?: Jenkins
Enter the following values (leave empty to omit):
✔ GitHub handle used to authenticate with the GitHub Container Registry: mona
✔ Personal access token to authenticate with the GitHub Container Registry: ***************
✔ Personal access token for GitHub: ***************
✔ Base url of the GitHub instance: https://github.com
✔ Personal access token for Jenkins: ***************
readme.md
+2 -3
View File
@@ -1,10 +1,9 @@
# GitHub Actions Importer labs
[GitHub Actions Importer](https://docs.github.com/en/actions/migrating-to-github-actions/automating-migration-with-github-actions-importer) helps plan, forecast, and automate the migration of Azure DevOps, CircleCI, GitLab, Jenkins, and Travis CI pipelines to GitHub Actions. This repository contains learning paths that teach you how to use GitHub Actions Importer and how to approach migrations to Actions.
> **Note**: GitHub Actions Importer is currently available as a public preview. Visit the [sign up page](https://github.com/features/actions-importer/signup) to request access to the preview.
[GitHub Actions Importer](https://docs.github.com/en/actions/migrating-to-github-actions/automating-migration-with-github-actions-importer) helps plan, test, and automate the migration of Azure DevOps, CircleCI, GitLab, Jenkins, and Travis CI pipelines to GitHub Actions. This repository contains learning paths that teach you how to use GitHub Actions Importer and how to approach migrations to Actions.
## Choose your learning path
To get started:
1. Use the `actions/importer-labs` repository as a template to [generate](https://github.com/actions/importer-labs/generate) a new GitHub repository.
travis/1-configure.md
+1 -5
View File
@@ -13,7 +13,7 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
- Click `Personal access tokens` and then `Tokens (classic)` (if present).
- Click `Generate new token` and then `Generate new token (classic)`. You may be required to authenticate with GitHub during this step.
- Name your token in the `Note` field.
- Select the following scopes: `workflow` and `read:packages`.
- Select the following scope: `workflow`.
- Click `Generate token`.
- Copy the generated PAT and save it in a safe location.
@@ -28,8 +28,6 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
- Select the `TERMINAL` tab from within the codespace terminal.
- Run the following command: `gh actions-importer configure`.
- Use the down arrow key to highlight `Travis CI`, press the spacebar to select, and then press enter to continue.
- At the GitHub handle prompt, enter the GitHub username used to generate the GitHub PAT in step 3 and press enter.
- At the GitHub Container Registry prompt, enter the GitHub PAT generated in step 2 and press enter.
- At the GitHub PAT prompt, enter the GitHub PAT generated in step 2 and press enter.
- At the GitHub URL prompt, enter the GitHub instance URL or press enter to accept the default value (`https://github.com`).
- At the Travis CI token prompt, enter the Travis CI access token from step 2 and press enter.
@@ -40,8 +38,6 @@ You will need to complete all of the setup instructions [here](./readme.md#confi
$ gh actions-importer configure
✔ Which CI providers are you configuring?: Travis CI
Enter the following values (leave empty to omit):
✔ GitHub handle used to authenticate with the GitHub Container Registry: mona
✔ Personal access token to authenticate with the GitHub Container Registry: ***************
✔ Personal access token for GitHub: ***************
✔ Base url of the GitHub instance: https://github.com
✔ Personal access token for Travis CI: ***************