Backend Infra team is planning to enable and standardize backend GitHub repository and workflow starting in 2018Q3. The main goal is to have a more reliable and highly available managed git repository and code review server. GitHub also comes with better integration with other development tools and extensible workflow using GitHub Apps. Along with the migration to GitHub, we also want to propose our git workflow recommendation.

Timeline Milestones

August 2018: Account Registration and Invitation, GitHub Pilot Projects
September W1, 2018: Git Workflow Socialization and Trial session
September W2, 2018: GitHub Repository Migration
September W3, 2018: GitHub is backend's main repository and code review server for new application repositories

Bear in mind that this new workflow and migration DOES NOT apply to backend-monorepo. Its development will still be done in Phabricator. Please read monorepo migration announcement and consult @fajrin or @christianto.handojo if you want to separate your codes to another repository.
Backend-monorepo-only developers should still secure their seat in the traveloka GitHub organization, to be able to access/contribute to other repositories

I. Registration and Invitation Period
If you haven't been recently invited to traveloka GitHub organization (check your email), you should create a GitHub user invitation request ticket to IT Helpdesk, soon. You have to register, add your @traveloka.com email address, and set up some keys first. Here are some pointers to help you be ready:

Register
Link URL: https://github.com/join
Adding @traveloka.com email address
Link URL: https://github.com/settings/emails
Adding SSH key
Link URL: https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/
Adding GPG key (optional, for now)

Link URL: https://help.github.com/articles/adding-a-new-gpg-key-to-your-github-account/

create a GitHub team for their respective team. Please name it with `backend-` prefix, and put the team under the backend team. Sub-teams may be created when necessary.

documented the recommended git workflow for application repositories

please give your feedback for the workflow, so we can improve it!

created a dummy application repository. You should try to do the actions below in the repository to familiarize yourself with the new git workflow in GitHub

fork the repository
make changes in your fork repository's feature branch
create a pull request of your feature branch
review each other's pull request
merge the pull request to the main branch
trigger the application release build in Jenkins
tag a production-released commit
monitor client module release progress in AWS CodeBuild

There will be a session demoing the new git workflow in GitHub in this period.

III. GitHub Repository Migration Period
You should migrate your backend application repositories in this period. Read how in our GitHub Repository Guide

IV. GitHub is backend's main repository and code review server
Backend developers are expected to start developing their application repositories in GitHub and use it heavily as the main git repository and code review server by Mid September, 2018

Backend GitHub Migration Plan