From e91983ab1b7c8d1304ce95ffbb7ad6725943812e Mon Sep 17 00:00:00 2001 From: Andrew Adams Date: Tue, 15 Sep 2026 12:55:39 -0700 Subject: [PATCH 1/2] Update code of conduct to require ai notices on communication --- .claude/CLAUDE.md | 4 +++- CODE_OF_CONDUCT.md | 7 +++++-- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md index 417c363a3b3e..156a61e5bf8b 100644 --- a/.claude/CLAUDE.md +++ b/.claude/CLAUDE.md @@ -108,8 +108,10 @@ It runs `clang-format` (C++, sorted includes), `clang-tidy` (via benchmarks in the PR description. - Keep unrelated fixes out of feature/bugfix PRs, even tempting drive-by CI fixes — open a separate PR. -- AI-assisted contributions require a `Co-authored-by:` trailer identifying the +- AI-assisted commits require a `Co-authored-by:` trailer identifying the tool (see `CONTRIBUTING.md` for the exact format Halide expects). +- Any AI-assisted github comments or PR descriptions require a 'Generated with' + footer that names the tool used. - Documentation, comments, and tutorials should match the existing style and prose — keep explanations simple and concise. If a change makes any of these out of date, identify and update them to match the implementation. diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index cfa43d653392..82ea3bd60134 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -55,8 +55,11 @@ that end, we have a few ground rules that we ask people to adhere to: beyond any requirements placed on you by the license of the original code. Additionally, any code generated by an AI tool (such as a large language model) must be clearly identified as such in the commit message using - "Co-authored-by: The name of the tool". We all like recognition for our work. - To that end... + "Co-authored-by: The name of the tool". Any communication to other Halide + developers or users that was substantially AI-authored must also be clearly + identified as such with a footer that says "Generated with (the name of + the tool)". This includes github comments and PR descriptions. We all like + recognition for our work. To that end... **Acknowledgements.** This code of conduct is a mix of [LLVM's](https://llvm.org/docs/CodeOfConduct.html) and From 562752e61aa1613cf8c7c0678fc52c689d851929 Mon Sep 17 00:00:00 2001 From: "halide-ci[bot]" <266445882+halide-ci[bot]@users.noreply.github.com> Date: Tue, 15 Sep 2026 20:21:50 +0000 Subject: [PATCH 2/2] Apply pre-commit auto-fixes --- .claude/CLAUDE.md | 4 ++-- CODE_OF_CONDUCT.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md index 156a61e5bf8b..40317ec7611b 100644 --- a/.claude/CLAUDE.md +++ b/.claude/CLAUDE.md @@ -108,8 +108,8 @@ It runs `clang-format` (C++, sorted includes), `clang-tidy` (via benchmarks in the PR description. - Keep unrelated fixes out of feature/bugfix PRs, even tempting drive-by CI fixes — open a separate PR. -- AI-assisted commits require a `Co-authored-by:` trailer identifying the - tool (see `CONTRIBUTING.md` for the exact format Halide expects). +- AI-assisted commits require a `Co-authored-by:` trailer identifying the tool + (see `CONTRIBUTING.md` for the exact format Halide expects). - Any AI-assisted github comments or PR descriptions require a 'Generated with' footer that names the tool used. - Documentation, comments, and tutorials should match the existing style and diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 82ea3bd60134..75a4e18b2fb8 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -57,8 +57,8 @@ that end, we have a few ground rules that we ask people to adhere to: model) must be clearly identified as such in the commit message using "Co-authored-by: The name of the tool". Any communication to other Halide developers or users that was substantially AI-authored must also be clearly - identified as such with a footer that says "Generated with (the name of - the tool)". This includes github comments and PR descriptions. We all like + identified as such with a footer that says "Generated with (the name of the + tool)". This includes github comments and PR descriptions. We all like recognition for our work. To that end... **Acknowledgements.** This code of conduct is a mix of