GitHub Handbook
Onboarding to GitHub.com
Helpful links to get you onboarded into GitHub.com, in the VA organization on GitHub.com and learning how to use GitHub.
Migration Process
The GitHub team is here to help you migrate from Rational to GitHub Enterprise Cloud (GitHub.com). If you’re already working with CM on your migration to GitHub.com, great, keep going! If you haven’t started working with us or CM, then let’s get started!
All teams should be migrated by end of September 2020 allowing time for validation and any additional clean-up
Step 1: Migration kick-off call
A one hour meeting with the VA GitHub Services Team where we’ll discuss your repos in Rational and build the plan for your migration.
Your post-call homework
- Complete a migration readiness checklist
- Decide when you can migrate (release schedules etc)
- Resource planning
Scheduling Migration Request
Submit GitHub - Migration Request issue (must be a member of the VA org)
Step 2: Workflow Consultations
(optional, but highly recommended)
A one hour call with the VA GitHub Services Implementation Engineers to evaluate your current state workflows and how they can be modernized and optimized in GitHub. We will also discuss your teams current knowledge of GitHub and Git and make a plan to help them trained for the changes ahead.
Schedule Workflow Consultation
Submit GitHub - Workflow Consultation issue (must be a member of the VA org)
Step 3: Security Consultations
(optional, but encouraged)
A one hour meeting with the VA GitHub Services Security team. This is for teams that would like information about how to turn on Security alerts, review security policy, security advisories, dependency vulnerability detection, secrets scanning, and code scanning features and workflows
Schedule Security Consultation (optional)
Submit Security Consultation issue (must be a member of the VA org)
Step 4: Automation Consultations
(optional, but encouraged)
A one hour meeting with the VA GitHub Services DevOps team for teams who are building automation or interested in building automation into your workflows and would like information on how to use and incorporate GitHub Actions.
Schedule Automation Consultation (optional)
Submit GitHub - Automation Consultation issue (must be a member of the VA org)
Tool Integrations
GitHub.com integrates with lots of VA DevOps tools which can be discussed during the migration kick-off call. The DOTS team will help you get set up with other tools that you may need.
Migration Readiness Checklist
Items the project team needs to be prepared for migration for the different legacy tools.
Rational
- Identified all baselines that you want to migrate
- Have a workflow migration
- GitHub Flow vs. Git Flow for branching strategy
- Check repository for:
- Large Files (need for Git LFS)
- Sensitive Data
- Identify and provide a list of the users that need access
- If no teams already, they will be created
- Permission levels for each team
- Resources for migration designated
- Product/Project manager
- Developer
VAEC (github.va)
- Coordination between VAEC team (Michael Taylor), project team, and the GitHub.com Services team
- Scheduling has to be precise due to downtime
Helpful Resources
- GitHub Onboarding information
- Previously Recorded Webinars
- GitHub Office Hours
Even Weeks: Tuesdays @ 10:00 AM Eastern
Odd Weeks: Wednesdays @ 2:00 PM Eastern
Zoom Meeting Link; Password is 1337
Contact Us
The VA GitHub Services Delivery team is here to help you not only before and during your migration. We are also here to help you well beyond your move into GitHub. Information on how you can connect with the GitHub Services Delivery team supporting the Department of Veterans Affairs can be found here