Production builds of the doc site now uses a dedicated shards override file that builds from docs branch of each component repo. This makes it possible to cherry pick commits from master into docs, then manually trigger a build without needing to do a release just to pull the latest change.
When a release does happen, docs is reset back to what master is as the two should now be in-sync.
Production builds of the doc site now uses a dedicated shards override file that builds from
docsbranch of each component repo. This makes it possible to cherry pick commits from master intodocs, then manually trigger a build without needing to do a release just to pull the latest change.When a release does happen,
docsis reset back to whatmasteris as the two should now be in-sync.