[
https://issues.apache.org/jira/browse/LIVY-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Gaido resolved LIVY-1047.
-------------------------------
Fix Version/s: 0.10.0
Resolution: Fixed
> Update PR template to align with ASF Generative Tooling Guidance
> ----------------------------------------------------------------
>
> Key: LIVY-1047
> URL: https://issues.apache.org/jira/browse/LIVY-1047
> Project: Livy
> Issue Type: Improvement
> Reporter: Gabor Roczei
> Assignee: Gabor Roczei
> Priority: Major
> Fix For: 0.10.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> To align with the ASF Generative Tooling Guidance, we should update our [PR
> template|https://github.com/apache/incubator-livy/blob/master/.github/PULL_REQUEST_TEMPLATE]
> to include a section for tracking any generative AI tools used to author
> patches.
> [https://www.apache.org/legal/generative-tooling.html]
> {noformat}
> When providing contributions authored using generative AI tooling, a
> recommended practice is for contributors to indicate the tooling used to
> create the contribution. This should be included as a token in the source
> control commit message, for example including the phrase “Generated-by: ”.
> This allows for future release tooling to be considered that pulls this
> content into a machine parsable Tooling-Provenance file.{noformat}
> Here is the Apache Spark's template for reference:
> [https://github.com/apache/spark/blob/master/.github/PULL_REQUEST_TEMPLATE]
> {code:java}
> ### Was this patch authored or co-authored using generative AI tooling?
> <!--
> If generative AI tooling has been used in the process of authoring this
> patch, please include the
> phrase: 'Generated-by: ' followed by the name of the tool and its version.
> If no, write 'No'.
> Please refer to the [ASF Generative Tooling
> Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
> --> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
