Skip to content

Commit eb9f6ff

Browse files
committed
CONTRIBUTING: make it clear that AI-generated PRs are not welcome
Includes a pull request template which also warns against this. For the rationale behind this, please read the text in the CONTRIBUTING guide.
1 parent 3dcb08a commit eb9f6ff

File tree

2 files changed

+53
-0
lines changed

2 files changed

+53
-0
lines changed

.github/CONTRIBUTING.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,26 @@ Ongoing development will be done in the `develop` branch with merges to `main` o
2626
To contribute an improvement to this project, fork the repo, run `composer install`, make your changes to the code, run the unit tests and code style checks by running `composer check-all`, and if all is good, open a pull request to the `develop` branch.
2727
Alternatively, if you have push access to this repo, create a feature branch prefixed by `feature/` and then open an intra-repo PR from that branch to `develop`.
2828

29+
### Words of Warning
30+
31+
#### Do Not Violate Copyright
32+
33+
Only submit a PR with your own original code. Do NOT submit a PR containing code which you have largely copied from an externally available sniff, unless you wrote said sniff yourself.
34+
Open source does not mean that copyright does not apply.
35+
Copyright infringements will not be tolerated and can lead to you being banned from the repo.
36+
37+
#### Do Not Submit AI Generated PRs
38+
39+
The same goes for (largely) AI-generated PRs. These are not welcome as they will be based on copyrighted code from others without accreditation and without taking the license of the original code into account, let alone getting permission for the use of the code or for re-licensing.
40+
41+
Aside from that, the experience is that AI-generated PRs will be incorrect 100% of the time and cost reviewers too much time.
42+
Submitting a (largely) AI-generated PR will lead to you being banned from the repo.
43+
44+
### Licensing
45+
46+
By contributing code to this repository, you agree to license your code for use under the
47+
[MIT license](https://github.com/WordPress/WordPress-Coding-Standards/blob/main/LICENSE).
48+
2949
# Considerations when writing sniffs
3050

3151
## Public properties

.github/pull_request_template.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
<!-- Provide a general summary of your changes in the title above. -->
2+
3+
<!--
4+
============================================================================================
5+
Warning: AI generated PRs are NOT welcome and will get you banned from this repo.
6+
7+
Please read the CONTRIBUTING guide before submitting your pull request.
8+
9+
Also please make sure your pull request passes all continuous integration checks.
10+
PRs which are failing their CI checks will likely be ignored by the maintainers.
11+
12+
Small PRs using atomic, descriptive commits are hugely appreciated as it will make
13+
reviewing your changes easier for the maintainers.
14+
15+
============================================================================================
16+
-->
17+
18+
# Description
19+
<!--
20+
What do you want to achieve with this PR? Why did you write this code? What problem does this PR solve?
21+
Describe your changes in detail and, if relevant, explain which choices you have made and why.
22+
-->
23+
24+
25+
## Suggested changelog entry
26+
<!--
27+
Please provide a short description of the change for the changelog.
28+
-->
29+
30+
31+
## Related issues/external references
32+
33+
Fixes #

0 commit comments

Comments
 (0)