@@ -93,6 +93,10 @@ Once a PR is created, a member of the ROOT team will review it as quickly as pos
9393ROOT community, it may be beneficial to add a suggested reviewer to the PR in order to get quicker attention.
9494Please ping people :wave: should you not get timely feedback, for instance with ` @root-project/core ping! `
9595
96+ > [! IMPORTANT]
97+ > For compatibility with our CI, your should create your PR with a ** branch name different from ` master` ** .
98+ > The branch name should ideally reflect the work being done in the PR, but this is not a hard requirement.
99+
96100# # Tests
97101
98102As you contribute code, this code will likely fix an issue or add a feature.
@@ -132,3 +136,19 @@ Some tests are run only outside the PR testing system:
132136we might come back to you with additional reports after your contribution was merged.
133137
134138Thank you for reading this; and even more: thank you :bouquet: for considering to contribute!
139+
140+ # # LLM Disclosure
141+
142+ Contributors are required to disclose whether the proposed changes (code or otherwise) were automatically generated
143+ by an LLM / " AI agent" .
144+
145+ The changes must in all cases have been * thoroughly reviewed and understood* by the contributor, who has full responsibility over them.
146+
147+ Please avoid proposing LLM-generated changes as-is without a full review and understanding, as this disrespects
148+ the reviewers' time and may cause your future contributions to be automatically rejected if reiterated.
149+
150+ Likewise, PR comments and any sort of engagement with other contributors must not be parroting LLMs or chatbots.
151+ At the reviewers' discretion, PRs suspected to contain low-effort copy-pasting from LLM tools may be closed.
152+
153+ In short, a tacit agreement of mutual respect is expected from all parties involved.
154+
0 commit comments