[fetch] Mark commits which touch .gitattributes as "interesting".

This check is a bit presumptuous; it assumes that all modifications to
.gitattributes files are interesting to recipes which is certainly not

However, the alternatives are tricky:

   1. Modify the gitattr checker logic in the recipe engine to see if
      the set of 'recipe files' changes with and without the .gitattributes
      modification. This would require probing a lot more data from git
      than the engine does currently.
   2. Load the diff of .gitattributes to see if it mentions the
      'recipes' tag. This is less work than option 1, and more accurate
      than the current CL, but still not totally accurate (though likely
      very close to perfect).

I think, for now, the current CL is a "good enough" approximation of the
correct behavior :)

R=lannm@chromium.org, martiniss@chromium.org, nodir@chromium.org

Bug: 938601
Change-Id: Idb5dff09b0f707d6eeb716ffe3d86c5d0b8d3e56
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1544893
Auto-Submit: Robbie Iannucci <iannucci@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
2 files changed
tree: 560cb3b14ab6ad4271f489d2598e01558d225645
  1. .gitattributes
  2. .gitignore
  3. .vpython
  9. README.md
  10. README.recipes.md
  11. codereview.settings
  12. doc/
  13. infra/
  14. misc/
  15. recipe_engine/
  16. recipe_modules/
  17. recipe_proto/
  18. recipes.py
  19. recipes/
  20. unittests/


Recipes are a domain-specific language (embedded in python) for specifying sequences of subprocess calls in a cross-platform and testable way.


  • README.md

    This file!

  • doc/

    Documentation for the recipe engine (including this file!). See the design doc for more detailed design information about the recipe engine.

  • infra/

    Chrome infra config files.

  • recipes.py

    The main entry point to the recipe engine. It has many subcommands and flags; run recipes.py -h to see them. Include this in your repository to start using recipes.

  • recipes/

    Recipes in the recipe engine. These are either example recipes, or recipes which are used to test the engine (see run_test.py to see these run)

  • recipe_modules/

    Built in recipe modules. These are very useful when writing recipes; take a look in there, and look at each of their examples subfolders to get an idea how to use them in a recipe.

  • recipe_engine/

    The core functionality of the recipe engine. Noteworthy files include:

    • main.py -- The main entrypoint for the recipe engine.
    • recipes_cfg.proto -- The protobuf file which defines the format of a recipes.cfg file.
    • third_party/ -- third_party code which is vendored into the recipe engine.
    • recipe_api.py -- The api exposed to a recipe module.
    • unittests -- Unittests for the engine.

    There are also several files which correspond to a subcommand of recipes.py; run, and autoroll are some examples.

  • unittests/

    Somewhat poorly named, these are higher level integration tests.


  • Sign the Google CLA.
  • Make sure your user.email and user.name are configured in git config.

Run the following to setup the code review tool and create your first review:

git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $HOME/src/depot_tools
export PATH="$PATH:$HOME/src/depot_tools"
git checkout -b work origin/master

# 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.