Skip to content

Conversation

@vbvictor
Copy link
Contributor

After #172515, we have a new paragraph in LLVM policy about AI:

The one exception we reserve is for GitHub issues labelled with the “good first issue” label. These issues are selected by LLVM contributors to help newcomers get familiar with the code base. Thus, it makes no sense to fix them using AI tools. Using AI tools to fix issues labelled as “good first issues” is forbidden.

We should add disclosure about it in the introduction note for developers to see clearly.

1. Check that no other contributor is working on this issue. If someone is assigned to the issue or claimed to be working on it, ping the person. After one week without a response, the assignee may be changed.
1. Leave a comment indicating that you are working on the issue, or just create a [pull request](https://github.com/llvm/llvm-project/pulls) after following the steps below. [Mention](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) this issue in the description of the pull request.
1. Fix the issue locally.
1. Fix the issue locally. Note that using AI tools to fix is forbidden by [LLVM Developer Policy](https://llvm.org/docs/DeveloperPolicy.html#ai-generated-contributions).
Copy link
Contributor Author

@vbvictor vbvictor Dec 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you have a better wording, suggestions are welcome.

There are some suggestions from AI, maybe you like it more:

  • Fix the issue locally, but do not use AI tools, as this is prohibited by the LLVM Developer Policy.
  • Fix the issue locally without using AI tools. The LLVM Developer Policy prohibits AI usage for "good first issues".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant