[roll] Roll infra/recipes [submodule_roller] Use git update-index

This saves a couple steps by letting us update a submodule's pinned
revision without actually cloning any submodules. This is required for
submodules with `update = none` in .gitmodules, i.e. configured to never
be checked out, which is a solution we might end up using for
fuchsia.git.

This required updating the auto_roller module to use `git status` to
check for staged changes instead of `git ls-files`, which doesn't
consider submodules that haven't been initialized.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1170332
Original-Revision: 92b62fdd208bbcccf0fff2b765d63dcd978aca78
GitOrigin-RevId: e85ac0d519d1c6ed0a081ae3a7cb6b67b6368e4e
Change-Id: Ic18e6d08a77bc39ecf539bd4c2166fb2e0008269
1 file changed
tree: 8a9b04b81330b4c8b7192885a74135bdaf2000bf
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.