Skip to content

Commit 86d1584

Browse files
committed
4.11
1 parent 2c094bd commit 86d1584

1 file changed

Lines changed: 11 additions & 24 deletions

File tree

docs/contributing.html

Lines changed: 11 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1523,30 +1523,17 @@
15231523
<div><h1 id="contributing">Contributing</h1>
15241524
<p>I am excited that you're considering contributing to our project! Here are some guidelines to help you get started.</p>
15251525
<hr>
1526-
<p>If you encounter a bug or have an enhancement suggestion, please check the "Issues" section of our GitHub repository or visit our official website for guidance before beginning any work on it.</p>
1527-
<p>I am excited that you're considering contributing to our project! Here are some guidelines to help you get started.</p>
1528-
<p>We primarily accept security fixes and critical patches to maintain project stability and coherence. Feature updates are not accepted to preserve our backend architecture and overall project integrity.</p>
1529-
<p>Below is an example of how to contribute to this GitHub project. Please follow this guideline and all other contribution rules carefully; otherwise, your request may be denied.</p>
1530-
<ul>
1531-
<li>Fork the repository to create your own copy.</li>
1532-
<li>Create a new branch for your changes (e.g., feature/my-feature).</li>
1533-
<li>Make your changes and verify everything works correctly.</li>
1534-
<li>Commit your changes with clear and concise messages.</li>
1535-
<li>Push your branch to your forked repository.</li>
1536-
<li>Open a pull request to the main repository’s main branch with a detailed description of your changes.</li>
1537-
<li>Reference any related issues or discussions in your pull request.</li>
1538-
</ul>
1539-
<p>To ensure your implementation is effective and maintainable by other developers, please follow the code quality guidelines outlined below.</p>
1540-
<ul>
1541-
<li>Keep your code clean and well-organized.</li>
1542-
<li>Add comments to explain complex logic or functions.</li>
1543-
<li>Use meaningful and consistent variable and function names.</li>
1544-
<li>Break down code into smaller, reusable functions and components.</li>
1545-
<li>Follow proper indentation and formatting practices.</li>
1546-
<li>Avoid code duplication by reusing existing functions or modules.</li>
1547-
<li>Ensure your code is easily readable and maintainable by others.</li>
1548-
</ul>
1549-
<p>If you encounter a bug or have an enhancement suggestion, please check the "Issues" section of our GitHub repository or visit our official website for guidance before beginning any work on it.</p></div>
1526+
<p>Thank you for your interest in this project.<br />
1527+
<br />
1528+
At this time, this repository is <b>not open for external contributions</b>. <br />
1529+
Please do <b>not</b> submit pull requests or patches.<br />
1530+
<br />
1531+
- Pull requests from external contributors are not accepted.<br />
1532+
- Any unsolicited pull requests will be closed without review.<br />
1533+
- All code in this repository is maintained by the project owner.<br />
1534+
- By design, no third‑party code will be merged into this project via GitHub.<br />
1535+
<br />
1536+
If you encounter a bug or have an enhancement suggestion, please check the "Issues" section of our GitHub repository or visit our official website for guidance before beginning any work on it.</p></div>
15501537

15511538

15521539

0 commit comments

Comments
 (0)