From 7e02d30a9d4db2ae280a01fd307ceb26a00895c7 Mon Sep 17 00:00:00 2001 From: Dylan Perks Date: Sun, 26 Jul 2026 17:27:12 +0100 Subject: [PATCH 1/9] Initial AI contribution guidelines --- CONTRIBUTING.md | 81 ++++++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 73 insertions(+), 8 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ad7c028a84..a83ebffbea 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -5,25 +5,82 @@ You can contribute to Silk.NET with issues and PRs. Simply filing issues for pro ## Considerations The Silk.NET team will merge changes that improve the library significantly. We will not merge changes that have narrowly-defined benefits, or are breaking in some way. All contributions must also follow all other guidelines outlined in this document. -## DOs and DON'Ts +### The TLDR + Please: -- **DO** talk to us in #team-talk in the Discord or open a discussion issue if your contribution is sizeable. +- **DO** talk to us in #team-talk in the Discord or open a discussion about your contribution - **DO** keep the discussions around contributions focused. If you have another matter to discuss, rather than creating a massive tangent in the current discussion, open up a new one. - **DO** follow the code of conduct if discussing on GitHub and/or the Discord #rules if discussing on Discord. +- **DON'T** use AI for your contribution without reading and understanding the nuance of doing so captured in this document. +- **DON'T** use AI in such a way that removes you as the human contributor from the process of understanding the code you're reading/writing, making technical decisions, documenting your contribution, and/or responding to the team/review comments. - **DON'T** make PRs that don't directly affect the end user, such as style changes. These are best done as part of a PR related to the area in question. Documentation is fine (and encouraged!), as this is useful to the end user. - **DON'T** commit code you didn't write without following its license and following our guidelines for doing so in the Contributor License Agreement. If you are unable to license some code, don't commit it. - **DON'T** surprise us with big pull requests or big API changes without talking to us first! - **DON'T** make PRs for legal or administrative documents, such as the license, file headers, or code of conduct. If you see something off, let us know and we'll change it. + +### Unannounced Contributions (including AI "drive-by" contributions) -## Breaking changes -Contributions must maintain API signature and behavioral compatibility. Contributions that include breaking changes will be rejected. There are exceptions to this, such as if the contribution is made against a major/breaking version branch (such as `2.0` instead of `master`), however this is subject to the team's approval. At risk of sounding like a broken record, talk to us about your idea first! +You **MUST NOT** submit unannounced sizeable contributions without first discussing it with the Silk.NET team. -### Generated bindings -Sometimes upstream specification changes happen while working on your contribution. Unfortunately, we are not in control of breaking changes created by the upstream spec sources, and if one happens while working on your contribution it is not a cause for concern. +**This includes both AI-generated contributions and non-AI-generated contributions.** -If your contribution affects binder output, let us know by commenting on the pull request. If the change isn't as a result of your modifications to the BuildTools (if any), it is recommended that you don't commit the .gen.cs files and instead do this in a separate PR. +Silk.NET is vehemently against AI "drive-by" contributions (i.e. where a large amount of work has been submitted by someone unfamiliar to the team), and we will reject any PR where we suspect this is the case. The simple way to avoid this is to talk to us before contributing anything sizeable. + +#### What is "sizeable"? + +Sizeable means any of the following: +- Affects tens of files or over a thousand lines of code. +- Affects the public API surface in a way that has not been approved through the [proposals process](documentation/proposals/README.md) if applicable. + +Generally speaking, a pull request that addresses an open issue (that, ideally, is marked as "help wanted", but we acknowledge that this might not always be the case) can be worked on without first consulting the Silk.NET team, provided it does not meet any of the above criteria. + +#### What is "unannounced" + +We would much rather you announce that you're working on something to us before you work on it (so we can plan maintainer workload and also guide you through any existing ideas that the team may have on what you're about to work on), but you **MUST** do so if it meets any of the above "sizeable" criteria. + +You **MUST** talk to us in #team-talk in the Discord, post an issue comment, and/or open a discussion issue if your contribution is sizeable (and **SHOULD** do so even if that isn't the case) + +### Use of AI + +When you're working on a contribution, you **MUST** be responsible and accountable for every line of code that you are contributing. + +You **MUST** be able to reason for, understand, and defend all technical aspects of your contribution. At the same time, you **MUST** be able to acknowledge and understand any review comments, and make informed decisions on how to action them. + +All technical decisions **MUST** be your own, and informed by your own understanding and ideally input from the Silk.NET team. AI can be used well for ideation (e.g. as a "sounding board"), but must be done so with sufficient understanding of the context to know when the AI is leading you astray. For the avoidance of doubt, the Silk.NET team can also be used in this way, and in fact we encourage this more than the AI alternative - we're always happy to lend time to help you help us with your contribution! + +Note that the above guidelines also apply for contributions where AI isn't used - if you don't understand what you've written or can't defend it, chances are we won't either. + +You **MUST** declare all AI usage, regardless of whether it is for code completion, review/comprehension, or generation of the contribution. + +AI generated documentation **MUST** be agreed with the Silk.NET team on a case-by-case basis. We will reject any pull request that contains AI-generated documentation that hasn't been explicitly approved by us ahead of time. -## Suggested workflow +### Human Communication + +As a general rule, even if AI is writing your code, we are still collaborating with you, not the AI. + +To this end, AI-generated descriptions, comments, or other forms of communication **MUST NOT** be used. If you have met the AI usage guideline, you don't need them. +AI-assisted translations or edits **MAY** be used in communication, but only where the original words prior to translation are your own. + +Silk.NET welcomes contributors with a diverse array of personalities, backgrounds, technical opinions/tastes, and way of working. +Effective self-expression is a key component of effective collaboration with us, we want to talk to a real human and that involves getting a feeling for your conduct/"voice". +This helps everyone understand where everyone's coming from, and helps establish middle-grounds in the event of differing opinions. + +You **MUST** follow the [Code of Conduct](CODE_OF_CONDUCT.md) at all times. + +You **SHOULD** communicate with the Silk.NET team using the #team-talk channel in our Discord, or via GitHub Discussions. +Where you are discussing a potential contribution, you **SHOULD** also discuss the mechanisms with which you intend to author your contribution (i.e. usage of AI tools) so we can be on the same page on what to expect. To be clear, we aren't going to force you into a specific way of working, but we want to manage our own expectations as well as ensure these guidelines are being followed. + +### Intellectual Property + +You **MUST NOT** use third party code without declaring it as per our Contributor License Agreement and ensuring the license is compatible with ours. +If you are ever in doubt, you **MUST** discuss this with the Silk.NET team. The .NET Foundation owns Silk.NET's intellectual property, and is by extension the risk owner of any potential infringements. +We can liase with the Foundation as needed. + +As per the "use of AI" section, you **MUST** declare any code that has been generated by AI. This does not automatically preclude the usage of AI-generated code on intellectual property grounds, rather it just manages the Silk.NET team's expectations. + +We understand AI usage is a sensitive issue from an intellectual property perspective. Large language models are known to make use of publicly-accessible material, however this does not automatically make the content licensable in an MIT-compatible way. The .NET Foundation has not established a stance on the intellectual property impact of AI usage, and in the advent of widespread LLM availability it has become the modus operandi for many software companies, teams, and individuals to make use of LLM output in copyrighted works in line with that LLM's terms and conditions. It is unknowable what materials (IP incumbered or not) were used in the production of specific output, whether that output is sufficiently transformative in the eyes of the law, and whether it is the LLM provider or the Foundation that owns the risk of infringement. We will follow industry trends/legal precedence in this stance as they develop. + +#### Early Pull Requests Silk.NET uses and encourages [Early Pull Requests](https://medium.com/practical-blend/pull-request-first-f6bb667a9b6). Please don't wait until you're done to open a PR! 1. Install [Git](https://git-scm.com/downloads) and the [.NET Core SDK](https://www.microsoft.com/net/download) @@ -34,6 +91,14 @@ Silk.NET uses and encourages [Early Pull Requests](https://medium.com/practical- 1. Make your commits in small, incremental steps with clear descriptions. 1. Tag a maintainer when you're done and ask for a review! +## Breaking changes +Contributions must maintain API signature and behavioral compatibility. Contributions that include breaking changes will be rejected. There are exceptions to this, such as if the contribution is made against a major/breaking version branch (such as `2.0` instead of `master`), however this is subject to the team's approval. At risk of sounding like a broken record, talk to us about your idea first! + +### Generated bindings +Sometimes upstream specification changes happen while working on your contribution. Unfortunately, we are not in control of breaking changes created by the upstream spec sources, and if one happens while working on your contribution it is not a cause for concern. + +If your contribution affects binder output, let us know by commenting on the pull request. If the change isn't as a result of your modifications to the BuildTools (if any), it is recommended that you don't commit the .gen.cs files and instead do this in a separate PR. + ## Working with our large solution The Silk.NET solution is **very large**. As such, to generate a solution that only has the projects you care about for your contribution, use the following command: From 5796dd627fc3955cc51753dffb65cdfa35b9605a Mon Sep 17 00:00:00 2001 From: Dylan Perks Date: Sun, 26 Jul 2026 17:37:35 +0100 Subject: [PATCH 2/9] Create AGENTS.md --- AGENTS.md | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 AGENTS.md diff --git a/AGENTS.md b/AGENTS.md new file mode 100644 index 0000000000..c123feff96 --- /dev/null +++ b/AGENTS.md @@ -0,0 +1,6 @@ +# AI Agent Guidelines + +AI agents are permissible for Silk.NET, but under strict guidelines. +- AI agents and their users **MUST** abide strictly by the [contribution guideliens](CONTRIBUTING.md). +- AI agents **MUST** request input from their user as required by the CONTRIBUTING guidelines (i.e. where technical decisions need to be made, these must not be done implicitly - the user of the AI agent **MUST** own every decision and understand it) +- AI agents **MUST** only interact with Git/GitHub in a read-only fashion - the user must be instructed to author commits and associated messages as needed. This is to ensure compliance with the "human communication" requirements in the CONTRIBUTING guidelines. From fda19b11f720b8e4f923e942aa027a3f888feed4 Mon Sep 17 00:00:00 2001 From: Dylan Perks Date: Sat, 8 Aug 2026 15:03:48 +0100 Subject: [PATCH 3/9] Update AI agent guidelines for contributions Clarified guidelines on AI agent usage for contributions, emphasizing that AI must not generate code and that human authorship is required for solutions to identified issues. --- AGENTS.md | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index c123feff96..2c45655a6b 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,6 +1,15 @@ # AI Agent Guidelines -AI agents are permissible for Silk.NET, but under strict guidelines. -- AI agents and their users **MUST** abide strictly by the [contribution guideliens](CONTRIBUTING.md). -- AI agents **MUST** request input from their user as required by the CONTRIBUTING guidelines (i.e. where technical decisions need to be made, these must not be done implicitly - the user of the AI agent **MUST** own every decision and understand it) -- AI agents **MUST** only interact with Git/GitHub in a read-only fashion - the user must be instructed to author commits and associated messages as needed. This is to ensure compliance with the "human communication" requirements in the CONTRIBUTING guidelines. +It is the current view of the maintainers that **AI must not be used** to generate code for contributions to this project. +There is no appetite on the current maintainers team to review the contributions of or collaborate with AI-assisted developers. +This policy is based on an ongoing consensus on the maintainers team. Should the consensus of the maintainers team change, this policy will be updated. + +"AI" in this case means a Large Language Model ("LLM"), such as ChatGPT, Claude, Copilot, Grok, etc. + +AI-generated code is based upon sources of unknown origins and may not be compatible with the MIT license, or may introduce conflicting license terms if they include code from other projects. + +AI can be used to identify issues with contributions to this project, but the solutions to those issues should be authored by humans. + +We have found that AI will frequently hallucinate issues that are not actually problems in practice, report incorrect information, and describe problems that are actually not issues at all. If AI identifies a problem with this codebase, please make sure you understand what it is saying and have independently confirmed that the issue exists before submitting a bug report or pull request. + +Any pull request to this project will ask you to confirm that you are the author and that you are contributing your changes under the Zlib license. From cd0e26ea7d5a3ed209aeccac809596af60c0bc0e Mon Sep 17 00:00:00 2001 From: Dylan Perks Date: Sat, 8 Aug 2026 15:07:37 +0100 Subject: [PATCH 4/9] Revise AI contribution guidelines in CONTRIBUTING.md Updated guidelines on AI usage for contributions, emphasizing the importance of human involvement and understanding in the contribution process. --- CONTRIBUTING.md | 25 ++++++++++--------------- 1 file changed, 10 insertions(+), 15 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a83ebffbea..75cde2507f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -11,8 +11,7 @@ Please: - **DO** talk to us in #team-talk in the Discord or open a discussion about your contribution - **DO** keep the discussions around contributions focused. If you have another matter to discuss, rather than creating a massive tangent in the current discussion, open up a new one. - **DO** follow the code of conduct if discussing on GitHub and/or the Discord #rules if discussing on Discord. -- **DON'T** use AI for your contribution without reading and understanding the nuance of doing so captured in this document. -- **DON'T** use AI in such a way that removes you as the human contributor from the process of understanding the code you're reading/writing, making technical decisions, documenting your contribution, and/or responding to the team/review comments. +- **DON'T** use AI to generate contributions for the project - **DON'T** make PRs that don't directly affect the end user, such as style changes. These are best done as part of a PR related to the area in question. Documentation is fine (and encouraged!), as this is useful to the end user. - **DON'T** commit code you didn't write without following its license and following our guidelines for doing so in the Contributor License Agreement. If you are unable to license some code, don't commit it. - **DON'T** surprise us with big pull requests or big API changes without talking to us first! @@ -22,8 +21,6 @@ Please: You **MUST NOT** submit unannounced sizeable contributions without first discussing it with the Silk.NET team. -**This includes both AI-generated contributions and non-AI-generated contributions.** - Silk.NET is vehemently against AI "drive-by" contributions (i.e. where a large amount of work has been submitted by someone unfamiliar to the team), and we will reject any PR where we suspect this is the case. The simple way to avoid this is to talk to us before contributing anything sizeable. #### What is "sizeable"? @@ -42,21 +39,23 @@ You **MUST** talk to us in #team-talk in the Discord, post an issue comment, and ### Use of AI -When you're working on a contribution, you **MUST** be responsible and accountable for every line of code that you are contributing. +It is the current view of the maintainers that AI **MUST NOT** be used to generate code for contributions to this project. +There is no appetite on the current maintainers team to review the contributions of or collaborate with AI-assisted developers. +This policy is based on an ongoing consensus on the maintainers team. Should the consensus of the maintainers team change, this policy will be updated. -You **MUST** be able to reason for, understand, and defend all technical aspects of your contribution. At the same time, you **MUST** be able to acknowledge and understand any review comments, and make informed decisions on how to action them. +"AI" in this case means a Large Language Model ("LLM"), such as ChatGPT, Claude, Copilot, Grok, etc. -All technical decisions **MUST** be your own, and informed by your own understanding and ideally input from the Silk.NET team. AI can be used well for ideation (e.g. as a "sounding board"), but must be done so with sufficient understanding of the context to know when the AI is leading you astray. For the avoidance of doubt, the Silk.NET team can also be used in this way, and in fact we encourage this more than the AI alternative - we're always happy to lend time to help you help us with your contribution! +AI-generated code is based upon sources of unknown origins and may not be compatible with the Zlib license, or may introduce conflicting license terms if they include code from other projects. -Note that the above guidelines also apply for contributions where AI isn't used - if you don't understand what you've written or can't defend it, chances are we won't either. +AI can be used to identify issues with contributions to this project, but the solutions to those issues should be authored by humans. -You **MUST** declare all AI usage, regardless of whether it is for code completion, review/comprehension, or generation of the contribution. +We have found that AI will frequently hallucinate issues that are not actually problems in practice, report incorrect information, and describe problems that are actually not issues at all. If AI identifies a problem with this codebase, please make sure you understand what it is saying and have independently confirmed that the issue exists before submitting a bug report or pull request. -AI generated documentation **MUST** be agreed with the Silk.NET team on a case-by-case basis. We will reject any pull request that contains AI-generated documentation that hasn't been explicitly approved by us ahead of time. +Any pull request to this project will ask you to confirm that you are the author and that you are contributing your changes under the Zlib license. ### Human Communication -As a general rule, even if AI is writing your code, we are still collaborating with you, not the AI. +As a general rule, we are still collaborating with you and your ideas, not that of any tools you may have used. To this end, AI-generated descriptions, comments, or other forms of communication **MUST NOT** be used. If you have met the AI usage guideline, you don't need them. AI-assisted translations or edits **MAY** be used in communication, but only where the original words prior to translation are your own. @@ -76,10 +75,6 @@ You **MUST NOT** use third party code without declaring it as per our Contributo If you are ever in doubt, you **MUST** discuss this with the Silk.NET team. The .NET Foundation owns Silk.NET's intellectual property, and is by extension the risk owner of any potential infringements. We can liase with the Foundation as needed. -As per the "use of AI" section, you **MUST** declare any code that has been generated by AI. This does not automatically preclude the usage of AI-generated code on intellectual property grounds, rather it just manages the Silk.NET team's expectations. - -We understand AI usage is a sensitive issue from an intellectual property perspective. Large language models are known to make use of publicly-accessible material, however this does not automatically make the content licensable in an MIT-compatible way. The .NET Foundation has not established a stance on the intellectual property impact of AI usage, and in the advent of widespread LLM availability it has become the modus operandi for many software companies, teams, and individuals to make use of LLM output in copyrighted works in line with that LLM's terms and conditions. It is unknowable what materials (IP incumbered or not) were used in the production of specific output, whether that output is sufficiently transformative in the eyes of the law, and whether it is the LLM provider or the Foundation that owns the risk of infringement. We will follow industry trends/legal precedence in this stance as they develop. - #### Early Pull Requests Silk.NET uses and encourages [Early Pull Requests](https://medium.com/practical-blend/pull-request-first-f6bb667a9b6). Please don't wait until you're done to open a PR! From fdd231abbf3866479c82ebd5196f00010ea299ba Mon Sep 17 00:00:00 2001 From: Dylan Perks Date: Sat, 8 Aug 2026 15:09:07 +0100 Subject: [PATCH 5/9] Update license confirmation from Zlib to MIT --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 2c45655a6b..88d03f6f75 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -12,4 +12,4 @@ AI can be used to identify issues with contributions to this project, but the so We have found that AI will frequently hallucinate issues that are not actually problems in practice, report incorrect information, and describe problems that are actually not issues at all. If AI identifies a problem with this codebase, please make sure you understand what it is saying and have independently confirmed that the issue exists before submitting a bug report or pull request. -Any pull request to this project will ask you to confirm that you are the author and that you are contributing your changes under the Zlib license. +Any pull request to this project will ask you to confirm that you are the author and that you are contributing your changes under the MIT license. From 0e21d415d8a68919794bf151483b70ecbeab808a Mon Sep 17 00:00:00 2001 From: Dylan Perks Date: Sat, 8 Aug 2026 15:09:23 +0100 Subject: [PATCH 6/9] Change license confirmation to MIT Updated the license confirmation from Zlib to MIT for pull requests. --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 75cde2507f..0f4160e9dd 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -51,7 +51,7 @@ AI can be used to identify issues with contributions to this project, but the so We have found that AI will frequently hallucinate issues that are not actually problems in practice, report incorrect information, and describe problems that are actually not issues at all. If AI identifies a problem with this codebase, please make sure you understand what it is saying and have independently confirmed that the issue exists before submitting a bug report or pull request. -Any pull request to this project will ask you to confirm that you are the author and that you are contributing your changes under the Zlib license. +Any pull request to this project will ask you to confirm that you are the author and that you are contributing your changes under the MIT license. ### Human Communication From 072a2321bac237d72542874caa0ab7dbd9d6b2d5 Mon Sep 17 00:00:00 2001 From: Dylan Perks Date: Sat, 8 Aug 2026 15:17:32 +0100 Subject: [PATCH 7/9] Update CONTRIBUTING.md --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0f4160e9dd..ca7e23b264 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -45,7 +45,7 @@ This policy is based on an ongoing consensus on the maintainers team. Should the "AI" in this case means a Large Language Model ("LLM"), such as ChatGPT, Claude, Copilot, Grok, etc. -AI-generated code is based upon sources of unknown origins and may not be compatible with the Zlib license, or may introduce conflicting license terms if they include code from other projects. +AI-generated code is based upon sources of unknown origins and may not be compatible with the MIT license, or may introduce conflicting license terms if they include code from other projects. AI can be used to identify issues with contributions to this project, but the solutions to those issues should be authored by humans. From e99a29b0164f688db4c933c44d75b5232ebadd96 Mon Sep 17 00:00:00 2001 From: Dylan Perks Date: Sat, 8 Aug 2026 15:30:55 +0100 Subject: [PATCH 8/9] Apply suggestions from code review Co-authored-by: William Chen Co-authored-by: Dylan Perks --- CONTRIBUTING.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ca7e23b264..b7f1421953 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -11,7 +11,7 @@ Please: - **DO** talk to us in #team-talk in the Discord or open a discussion about your contribution - **DO** keep the discussions around contributions focused. If you have another matter to discuss, rather than creating a massive tangent in the current discussion, open up a new one. - **DO** follow the code of conduct if discussing on GitHub and/or the Discord #rules if discussing on Discord. -- **DON'T** use AI to generate contributions for the project +- **DON'T** use AI to generate contributions for the project. - **DON'T** make PRs that don't directly affect the end user, such as style changes. These are best done as part of a PR related to the area in question. Documentation is fine (and encouraged!), as this is useful to the end user. - **DON'T** commit code you didn't write without following its license and following our guidelines for doing so in the Contributor License Agreement. If you are unable to license some code, don't commit it. - **DON'T** surprise us with big pull requests or big API changes without talking to us first! @@ -67,7 +67,6 @@ This helps everyone understand where everyone's coming from, and helps establish You **MUST** follow the [Code of Conduct](CODE_OF_CONDUCT.md) at all times. You **SHOULD** communicate with the Silk.NET team using the #team-talk channel in our Discord, or via GitHub Discussions. -Where you are discussing a potential contribution, you **SHOULD** also discuss the mechanisms with which you intend to author your contribution (i.e. usage of AI tools) so we can be on the same page on what to expect. To be clear, we aren't going to force you into a specific way of working, but we want to manage our own expectations as well as ensure these guidelines are being followed. ### Intellectual Property @@ -87,7 +86,7 @@ Silk.NET uses and encourages [Early Pull Requests](https://medium.com/practical- 1. Tag a maintainer when you're done and ask for a review! ## Breaking changes -Contributions must maintain API signature and behavioral compatibility. Contributions that include breaking changes will be rejected. There are exceptions to this, such as if the contribution is made against a major/breaking version branch (such as `2.0` instead of `master`), however this is subject to the team's approval. At risk of sounding like a broken record, talk to us about your idea first! +Contributions must maintain API signature and behavioral compatibility. Contributions that include breaking changes will be rejected. There are exceptions to this, such as if the contribution is made against a major/breaking version branch (such as `2.0` instead of `main`), however this is subject to the team's approval. At risk of sounding like a broken record, talk to us about your idea first! ### Generated bindings Sometimes upstream specification changes happen while working on your contribution. Unfortunately, we are not in control of breaking changes created by the upstream spec sources, and if one happens while working on your contribution it is not a cause for concern. From cae46e084901f2b47d4363f22f591a738beefdd1 Mon Sep 17 00:00:00 2001 From: Dylan Perks Date: Sat, 8 Aug 2026 15:33:12 +0100 Subject: [PATCH 9/9] Update pull request template with authorship confirmation Added a confirmation checkbox for authorship and licensing. --- .github/pull_request_template.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index c21ce7d41f..ad6beffd2f 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -1,6 +1,8 @@ # Summary of the PR A short summary of this PR and what it adds/removes/fixes. +- [ ] I confirm that I am the author of this code and release it to the Silk.NET project under the MIT license. This contribution does not contain code from other sources, including code generated by a Large Language Model ("AI"). + # Related issues, Discord discussions, or proposals Links go here.