commit | 443d5bec4540b1e2b324a9ba50406796aa2b26a2 | [log] [tgz] |
---|---|---|
author | Robert Iannucci <iannucci@chromium.org> | Thu May 04 16:45:30 2023 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 04 16:45:30 2023 |
tree | bcc11c71bd8b1b691d03207bca4176250c9c7fe4 | |
parent | fe30d36bce15efa9a1ef5a5feb32841f1683a8a7 [diff] |
[url/pycurl] Set default User-Agent header. This adds a User-Agent field to the Session headers (and gently refactors the other headers usage to allow overriding the User-Agent if desired). R=fancl Change-Id: I2975be0c15f0390571268fef39c4ae8e69b10a11 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/4505025 Auto-Submit: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Chenlin Fan <fancl@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
Recipes are a domain-specific language (embedded in Python) for specifying sequences of subprocess calls in a cross-platform and testable way.
They allow writing build flows which integrate with the rest of LUCI.
Documentation for the recipe engine (including this file!). Take a look at the user guide for some hints on how to get started. See the implementation details doc for more detailed implementation information about the recipe engine.
user.email
and user.name
are configured in git config
.Run the following to setup the code review tool and create your first review:
# Get `depot_tools` in $PATH if you don't have it git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $HOME/src/depot_tools export PATH="$PATH:$HOME/src/depot_tools" # Check out the recipe engine repo git clone https://chromium.googlesource.com/infra/luci/recipes-py $HOME/src/recipes-py # make your change cd $HOME/src/recipes-py git new-branch cool_feature # hack hack git commit -a -m "This is awesome" # This will ask for your Google Account credentials. git cl upload -s -r joe@example.com # Wait for approval over email. # Click "Submit to CQ" button or ask reviewer to do it for you. # Wait for the change to be tested and landed automatically.
Use git cl help
and git cl help <cmd>
for more details.