Web Repository Migration to GitHub

Starting next thursday (1 February 2018), frontend main web repository (where we host source code for www.traveloka.com and m.traveloka.com) will be migrated to GitHub as a requirement for PCI-DSS certification. This means that we no longer accept diff at phabricator, and we'll use GitHub as source of truth for master and release branch.

Phabricator remote still remains active for backup purpose in case there's a problem in release process (new release process from GitHub is not backward compatible).

Our new repository is hosted at https://github.com/traveloka/www (under traveloka organization). If you haven't joined traveloka GitHub organization or need access to main web repository please contact @web-infra team.

Repository migration process is as simple as changing your default remote (usually origin) to GitHub remote:

git remote set-url origin git@github.com:traveloka/www.git

For more information regarding migration process, branching model, and Pull Request can be seen in https://29022131.atlassian.net/wiki/spaces/ENG/pages/138936827/Frontend+Deployment+Git+Branching+Model.

FAQ
What happen when my diff hasn't landed to master on 1st February?

You need to create Pull Request to GitHub repository. If your local branch is no longer exist, you can use arc patch to checkout changes from phabricator locally and push that new branch created by arcanist.

I'M NO LONGER ABLE TO PUSH my branch TO ORIGIN REMOTE AFTER changing remote to github. WHAT SHOULD I DO?

We recommend pushing your own branch to your fork remote instead of main remote. This way remote branch in main remote is clean and only contains master and release branch. Pushing your branch to your fork remote also makes creating PR easier. More information can be seen in https://29022131.atlassian.net/wiki/spaces/ENG/pages/138936827/Frontend+Deployment+Git+Branching+Model.