[roll] Roll infra/recipes [cleanup] Move RunSteps to the top of every recipe file

As suggested by http://go/fuchsia-recipe-docs#function-ordering, it's
preferred for `RunSteps` to be the first function in every recipe
because it's the entrypoint, and because `GenTests` is suggested to be
the last function, it can be hard to locate `RunSteps` when it's the
second-to-last function as was the case in all of these recipes.

This unblocks us from enforcing the function ordering with shac.

The main downside is that we lose `git blame` history for the affected
lines, but we can work around that by adding this commit's final hash to
the `.git-blame-ignore-revs` file in a follow-up change, which will
exclude this commit from being considered by `git blame` if `git config
blame.ignoreRevsFile .git-blame-ignore-revs` is set.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/868357
Presubmit-Verified: CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com>
Original-Revision: d7bb1c93166487193756186c801a946bef625cf0
GitOrigin-RevId: a4534dab6aec7c88c9fe00ef71b383672b3f8f70
Change-Id: I22e67a881721fd9cd47e5bbbbc84afdd62b4c8e8
1 file changed
tree: 8962eef4b53c51c70b73c94481f382e12d1f5f4d
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.