Go to the parent directory of your iOS repository. For example, if your iOS repo is located at ~/Documents/traveloka-ios, then you need to go to Documents folder (i.e. cd ~/Documents).
rm -rf district-traveloka
git clone ssh://git@git.traveloka.com/diffusion/DRNTVLK/district-traveloka.git
cd district-traveloka
git submodule update --init ios (this will take a while..)
cd ios (this should be your working directory.)
git fetch
git checkout develop

The steps above should only be a one-time thing, and you don't need to worry about district-traveloka – at least for now.

The ios folder is a submodule. When you go inside the folder, Git automatically changes the context to the submodule's remote URI – i.e. the new iOS repository. In short, just perform all your usual work from the ios folder.

:warning: IMPORTANT

:warning: – Do not perform any git operations from the parent folder (i.e. district-traveloka) unless requested by Infra team!

In conclusion, if your previous iOS repository is located at ~/Documents/traveloka-ios, now your working directory should be ~/Documents/district-traveloka/ios.

What has changed?

:tada:

We're still using Phabricator.

Although we needed to fresh clone, we're still using Phabricator. The migration to Github will happen after 3.0 submission.

Repository truncation is (partially) successful.

The original plan was to truncate our Git repository from before 2017 – that means, all commits before 2017 will be squashed together into one commit. However, the trial was unsuccessful as we encountered many conflicts that may cause the result to have different state. Therefore, we decided to move forward with plan B, which is deleting large file blobs from our history with the help of BFG Repo Cleaner. In the end, we managed to achieve:

The new repo is mirrored to Github in near real-time.

This makes it easy for the infra team to test out integrations between Github and Bitrise, which we will start doing next week. This also makes it easy for us to move from Phabricator to Github later – simply by changing our remote URL.

Some Herald and Owner objects have been moved.

Herald objects' repositories cannot be changed once set, therefore we needed to create a new one. But everything has been tested to perform just like before, so you can rest assured!

Bitrise now builds from the new repository.

Old repository (rTVIOS) is now read-only.

We keep the old one only for historical reasons. It might be archived sometime in the future.

Additional Notes

:memo:

Utilize arc patch to move your ongoing revisions.

If you have local branches in old repository not yet pushed before repository block:

Do an arc diff ,
Go to the new repository, and
Perform arc patch.

If you have ongoing revision, that's under review or already accepted and ready to land:

Go to the new repository,
Perform arc patch.
Then, you can resume your work:

make changes and do another arc diff, or
arc land if your revision has been accepted.

An All-New Traveloka iOS Repository :tada:

Getting the new repository

What has changed? :tada: