[roll] Roll fuchsia [bazel][third_party] Track in Bazel files directly

... for mini_chromium and lss in fuchsia.git, instead of using opaque
git bundles. Thanks for the recent third_party layout migrations of
these dirs.

fx set minimal.x64
fx build bazel_workspace
fx bazel build \
  //third_party/mini_chromium:base \
  //third_party/linux-syscall-support

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/775743
Original-Revision: 223aec7e7c38ad2121cc6280516cba86090a942b
GitOrigin-RevId: a5b985bb193a23febf8b21291ad7dce65638a1c7
Change-Id: Id449d735ba746409cbf38b3cf4acbfd7c446c3bf
1 file changed
tree: 84b02a9ad57ba197f82ee609f45267903f34c45f
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.