Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ Commits should be as narrow in scope as possible.
Commits that span hundreds of lines across multiple unrelated functions and/or files are very hard for maintainers to follow.
After about a week they'll probably be hard for you to follow, too.

If using AI tools to assist with writing code, it is good to disclose this in the commit message, for example using the [`Assisted-by` trailer](https://docs.kernel.org/process/coding-assistants.html#attribution) as recommended by the Linux kernel project.

Please also avoid making minor commits for fixing typos or linting errors.
[Don’t forget to lint before you push!](https://soundcloud.com/lemonsaurusrex/lint-before-you-push)

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,8 @@ Whenever the assets are images, audio or even code, they must have a license com
5. **Follow the [Python Discord Code of Conduct](https://pydis.com/coc).**
We aim to foster a welcoming and friendly environment on our open source projects.
We take violations of our Code of Conduct very seriously, and may respond with moderator action.
6. **Disclose usage of AI.**
If you use AI tools to assist with your contributions, disclose this in the pull request description.

<br/>

Expand Down