[roll] Roll infra/recipes [submodule_roller] Force-clone the submodule to roll ... even if they have `update = none` in the .gitmodules file. It's not possible to update the submodule without cloning it. A previous attempt at rolling submodules with `update = none` (https://fxrev.dev/1170332) attempted to do it by skipping cloning the submodule and directly updating the git index. However, this didn't interact nicely with the auto_roller recipe module's no-op change detection logic, which didn't consider the submodule to be changed. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1170958 Original-Revision: ec1be15e19abe850ddb469c7bf35f5f79a076027 GitOrigin-RevId: 8dc58ed217cca66fada2cced77a7acc84a4cd74f Change-Id: I43145ad9cc2983e4b46e58b63da15fd67a5810e3
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.