// Use when creating commits or diffs to apply the correct title prefix, reviewer, and test plan based on the area of the codebase being changed.
| name | commit-conventions |
| description | Use when creating commits or diffs to apply the correct title prefix, reviewer, and test plan based on the area of the codebase being changed. |
| oncalls | ["pyre","pysa"] |
When creating commits:
[pysa] as a prefix in the commit title. Otherwise, add [pyre] as a prefix in the commit title.#pysa_swe as a reviewer. Otherwise, add #pyre as a reviewer.make test in the test plan.Use when you need to understand the Pyre or Pysa codebase architecture, find where specific functionality is implemented, or navigate the source directory structure. Use when working on OCaml code, debugging type checking or taint analysis issues, or exploring the codebase.
Use when debugging a Pysa false negative (missing taint issue), comparing two Pysa output directories, or finding where taint flow is lost.
Use when running, debugging, updating, or creating Pysa end-to-end integration tests. Use when taint analysis tests fail, when expected output files need updating, or when working with .models, .cg, .hofcg, .overrides files under `source/interprocedural_analyses/taint/test/integration`.
Use when reading, writing, or debugging Pysa JSON model output (.models files). Use when working with taint models that describe sources, sinks, TITO, sanitizers, or issues in JSON format.