| commit | ae0af3feb2deb7e6f9fa9c041a5878843a8e66c1 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Mon Jul 15 16:39:47 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 15 16:39:47 2024 +0000 |
| tree | 32af10c19c5d23d2b57ac82344fc4b3fff9f1566 | |
| parent | 1c505b318956209338b73ee6c5b5544b58e1f85a [diff] |
cipd_roller: Clean up commit message Ensure none of the regular commit message ends up in the footer, like it did in http://pwrev.dev/223011. Remove the colons since they aren't necessary and when manually making a roll locally they will tell the change-id hook that those lines are footers. (Not strictly relevant here, but people will likely copy this format for manual rolls.) Then, add a blank line after the last roll in the commit message. Bug: b/352815723 Change-Id: I253473be8b18687fd3b5f16da4d84742fc929bae Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/223071 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Ted Pudlik <tpudlik@google.com> Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com>
This repository contains recipes for Pigweed.
A recipe is a Python script that runs a series of commands, using the recipe engine framework from the LUCI project. We use recipes to automatically check out, build, and test Pigweed and downstream projects using Pigweed in continuous integration jobs. The commands the recipes use are very similar to the ones you would use as a developer to check out, build, and test Pigweed in your local environment.
See go/pigweed-recipe-docs for complete documentation and a guide for getting started with writing recipes.
The recommended way to get the source code is with git.
git clone https://pigweed.googlesource.com/infra/recipes
In most cases you will need a Chromium depot_tools checkout in your PATH as well.
git clone https://chromium.googlesource.com/chromium/tools/depot_tools ~/depot_tools echo 'export PATH="$PATH:$HOME/depot_tools"' >> ~/.bashrc
./presubmit.sh runs three different sets of tests:
./recipes.py test train)./black --diff --check .).recipe_deps/fuchsia/scripts/cleanup_deps.py --check)The formatting check will tell you what‘s wrong but not fix it. For that you need to run ./black .. Similarly, the dependencies check will tell you what’s wrong but you'll need to edit the files to fix issues.
If not using ./presubmit.sh you'll need to run ./scripts/ensure_black.sh before ./black is present.