From 9f6e4921c48c0767dd1d0b0d889734c7e66570f8 Mon Sep 17 00:00:00 2001 From: Jeremy Stanley Date: Fri, 23 May 2025 16:31:48 +0000 Subject: [PATCH] Comply with Policy for AI Generated Content While probably not meeting most people's definition of artificial intelligence these scripts do create patches. The OpenInfra Policy for AI Generated Content recommends to: > Add a "Generated-By:" label to the commit message, and explain in > comments or the commit message any prompts or background context > the reviewers might need to fully understand the change and how > much of the change was generated by the tool. Even though it also has a carve-out for these sorts of scripts: > The exception to the rule is that we do allow submissions from > well documented automated processes, such as release tooling or > for internationalization updates. https://openinfra.org/legal/ai-policy Nevertheless, documenting within the commit message the location of the script which was used to generate that contribution is helpful for a number of obvious reasons. Let's do it anyway, even though it's not technically required. Change-Id: I36c1a0a796781cdbc87a7e5f1058ae6afe14db4c --- tools/noop-change.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tools/noop-change.sh b/tools/noop-change.sh index 759a9d81af..ef17e46249 100755 --- a/tools/noop-change.sh +++ b/tools/noop-change.sh @@ -165,6 +165,7 @@ if [ -n "$change" ] ; then Depends-On: $change" fi -git commit -m "$commit_msg" -s +git commit -m "$commit_msg" -s \ + --trailer="Generated-By:openstack/requirements:tools/noop-change.sh" git review -t ${topic} # TODO(tonyb): Check for vote-a-tron and -W the change if it's available