This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
Travis CI to GitHub Actions Migration Guide converts a file you already hold. The Travis CI to GitHub Actions starter is partial. Secrets stay in the secret store. Do not enable the workflow. Delete auto-approve.
You do not convert a repository you do not own. The browser tool drafts text. It does not apply the result and it does not log in.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep. 10.0.0.0/16 is a sample prefix, not a network you publish unless you already use it.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the account named in the ticket. Read the draft, then the account, then decide.
Rollback is the previous file, the previous plan, or the lab resource you can delete because it was only a lab.
- Write the account, project, or repository, and confirm you administer it.
- Save the current file or export before any draft is applied.
- Read the draft and delete every line this ticket did not name.
- Replace account IDs, images, example.com, and any sample password.
- Apply nothing during the reading.
- Read the names back and compare them with the ticket.
- Stop. The next change is a different page.
Mistakes that outlive the statement
travis-gha conversion goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Applying a draft you did not read.
- The wrong account.
- A secret, an access key, or a kubeconfig in git.
- Two changes in one window.
- No copy saved before the change.
- A documentation address or example.com left in a file you apply.
- An ingress from 0.0.0.0/0 left in the file.
- Calling the generator output a finished production change.
- The Travis CI to GitHub Actions starter is partial. Secrets stay in the secret store. Do not enable the workflow. Delete auto-approve.
- Applying the sketch during the reading.
Decisions to write down
One decision for travis-gha conversion: The source file is one you hold. The rewrite is partial until a person has read it. Secrets are not in the new file. Nothing was applied or enabled. And the destination is the one in the title.
Checks before you call it done
Confirm this before you call the change done: The source is named. The sketch was read. No secret is in the new file. Nothing was applied. Nothing was enabled. And a second person can say what is still unmapped. If one of those fails, stop.
# Partial conversion. Review every name.
# The Travis CI to GitHub Actions starter is partial. Secrets stay in the secret store. Do not enable the workflow. Delete auto-approve.
# 192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep. 10.0.0.0/16 is a sample prefix, not a network you publish unless you already use it.Before you leave the account
Travis CI to GitHub Actions Migration Guide ends when the account in the note is the account in the ticket. If it is not, stop.
The draft stays a draft until a person has read the names in it. A generator does not log in, does not apply, and does not scan.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep. 10.0.0.0/16 is a sample prefix, not a network you publish unless you already use it.
prompt-for-this is a reminder that a secret is missing. It is not an access key, a token, or a password you save. An Azure secret draft may contain a sample password. Replace it. Do not file it.
One change is the window. If two things move and the result is wrong, you will not know which one did it.
If the same step fails twice, stop for the day. Restore the copy you took first.
A second person reads the account and the change aloud. If they cannot find them in the ticket, the note is not done.
This page is a planning guide. It is not a vendor manual, not an official standard, not legal advice, and not an audit opinion. You do not apply it against an account you do not administer.
Tools for this guide
This guide does not name a browser tool. The pillar it belongs to links the calculators for the neighbouring work.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.