[Important] Migrate to GitHub for Cobalt Development!
Lam Bui
TL;DR; Cobalt developers must migrate to the Cobalt GitHub repo (https://github.com/youtube/cobalt). The googlesource repository (https://cobalt.googlesource.com/cobalt) is now deprecated and will be removed.
Cobalt has migrated to GitHub! Please migrate your local development to use GitHub as upstream moving forward. We planned this shift over the past few years to make quality of life improvements for all Cobalt developers based on developer feedback. Migrating to GitHub streamlines Cobalt development while setting up Cobalt to take advantage of industry tools and processes already built into or seamlessly integrated with GitHub.
Some major improvements and benefits include:
Transparent upstream development
GitHub as the source of truth
Easier to understand changes with viewable specific commits per release
Individual features, fixes, and optimizations are separated (no more single squashed commit for an entire release)
Testing workflow results and Build Status are visible via GitHub Actions
More familiar external contributions process with the GitHub Pull Requests model
FAQs
My workflow already uses GitHub. Is there anything else that I need to do?
Nope! You can continue using Cobalt via the GitHub repository as you already have been.
I’m using Googlesource. What do I need to do?
You will need to do a fresh clone of the Cobalt GitHub repository (https://github.com/youtube/cobalt) and apply your changes on top of the baseline code. Sorry for the inconvenience, but this change makes all future development much simpler and more insightful for Cobalt developers.
Do I need to re-clone my local repository?
Yes. Re-clone from the Cobalt GitHub repository (https://github.com/youtube/cobalt) and rebase your changes.
Can I just point my Googlesource upstream to the new GitHub repository?
No. The history is different and requires a fresh re-clone of the GitHub repository for development.
 | • Lam Bui |
