[roll] Roll fuchsia [submodules] Add test submodule

... and an associated shac check that just prints the contents of the
submodule's README to confirm whether the submodule was checked out and
patched correctly.

This will be used to test submodules-as-source-of-truth workflows - all
previously existing submodules are still synced from Jiri manifests,
this is the first one that doesn't have a corresponding Jiri manifest
entry.

Original-Bug: 326595281
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/996492
Original-Revision: c4a3455d9a7471e6dcbb0582c3b98e38ed3ee3ca
GitOrigin-RevId: 9e9283258f6eec9a02e1a0352dc34c73076cd6b2
Change-Id: I1a6a33d575ed77d78e7f9e0d12050f8778ac4a7a
1 file changed
tree: e461f80779c096a334c5ac3c17589ce67527ef3b
  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 via the IRC channel #fuchsia on Freenode.

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.