[roll] Roll fuchsia [GEMINI.md] Allow individual 'fx build' targets

The command-line agent started to categorally refuse to run
`fx build <target>` even when I told it to do it, arguing that
the project's "safety" rules prevented it. When working heavily
on build rules, a full `fx build` is terribly slow and unnecessary
so this relaxes the text to allow for such usage in certain
cases.

Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1611551
Original-Original-Revision: 35e1fe630dec2a3ecfb1ba16b15960b88e31d23e
GitOrigin-RevId: e81132db1b8de6a1390d1023fa924c3600b426b3
Change-Id: Ida71941d91d3dfc66b15161710ce2e48526646a6
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1613913
Cr-Commit-Position: refs/heads/main@{#192900}
1 file changed
tree: 3a3194c87d18ddc2d6c15389ac2ec99ce2fc16bd
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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.