[ 
https://issues.apache.org/jira/browse/HDDS-17108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDDS-17108:
----------------------------------
    Labels: pull-request-available  (was: )

> Recommend Co-authored-by for assisted commits
> ---------------------------------------------
>
>                 Key: HDDS-17108
>                 URL: https://issues.apache.org/jira/browse/HDDS-17108
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Attila Doroszlai
>            Assignee: Attila Doroszlai
>            Priority: Major
>              Labels: pull-request-available
>
> ASF [policy on generative 
> tooling|https://www.apache.org/legal/generative-tooling.html] recommends 
> indicating usage of such tools in the commit message:
> bq. 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: <Name 
> of Tool> <Version>” or "Co-authored-by: <Name of Tool> <Version>".
> Ozone contributors' guide asks for "Generated-by" in the PR description.  
> This is easy to miss when merging pull requests, so the final commit may lack 
> this information even if the PR had it.
> I would like to recommend using {{Co-authored-by}} on commits in the PR 
> branch instead.  Benefits:
> - It is automatically picked up by GitHub's merge commit message.
> - Allows for the possibility of using different tools for commits in the PR, 
> or even no tools for some commits.
> - Accepting reviewer suggestions also uses this footer, so AI and human help 
> is acknowledged in the same way.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to