Initialize the repository and sync:
mkdir lineage_mirror cd lineage_mirror repo init -u https://git.replicant.us/replicant/manifest.git -b LineageOS-mirror repo sync
- Check the LineageOS manifest for newly added repos
- If there are any, add them in the LineageOS-mirror manifest and push the changes to git.replicant.us
- If there are any, create the newly added repos in the LineageOS-mirror group (using the exact same names the repos have in LineageOS)
- Update the local mirror with
- If there are newly added repos, you need to manually push them the first time in order to create the branch on the remote:
cd path/to/new/repo git push firstname.lastname@example.org:LineageOS-mirror/REPO_NAME HEAD:refs/heads/cm-13.0
Repeat these steps for all newly added repos.
- Push the updated branches to git.replicant.us:
repo forall -c ' echo "Pushing $REPO_PROJECT"; git push email@example.com:LineageOS-mirror/$( echo $REPO_PROJECT | cut -c11- ).git HEAD:cm-13.0 '
Check for errors during the push and fix them!
It's worth to check if all mirror repos have bundles in place.
If we ever add support for a device that uses CAF branches of Qualcomm repos, we need to figure out how the mirror can still be updated and how releases can be tagged.
CAF branches are in the same repos as the default branches. So two or more local repos are created for one remote repo when the default branch and the CAF branches are checked out. The current setup for tagging a new release and updating the mirror assumes that there is one local repo for one remote repo.