# Description of Changes
Marked the llm benchmark files as autogenerated so they are marked as
"autogenerated" in github diffs.
# API and ABI breaking changes
None
# Expected complexity level and risk
1
# Testing
- [x] They are marked correctly as autogenerated if I push a change to
those files
---------
Co-authored-by: Zeke Foppa <bfops@users.noreply.github.com>
* Commit test clients' module_bindings
Having discussed with the team, I've come around to it being correct
to commit the `module_bindings` for the SDK tests' two test clients.
This way, people not working on codegen can run `cargo test --workspace` &c,
and open the test clients with rust-analyzer without any additional rigamarole.
The downside is that any time codegen changes,
we'll see very large commits touching all of these files,
but consensus is we don't really care.
An additional upside is that now we can run clippy against the bindings in CI,
which will incentivize ensuring that the bindings generate lint-free code.
* Add linguist-generated=true for generated module bindings
* Top-level .gitattributes sets `module_bindings` as generated
Zeke Foppa