GH-306 Refactor PR Template, Contributing file, delete auto assign (#306)

* Refactor PR Template, Contributing file, delete auto assign

* Update .github/CONTRIBUTING.md

Co-authored-by: Jakubk15 <[email protected]>

* Update LICENSE

Co-authored-by: Jakubk15 <[email protected]>

Co-authored-by: Jakubk15 <[email protected]>

Author: vLuckyyy

.github/CONTRIBUTING.md

@@ -1,21 +1,30 @@
-# We have a few simple rules while making a new PR.
+# Contributing to EternalCore
+We welcome contributions to EternalCore! Whether you're fixing a bug, adding a new feature, or improving documentation, we're glad to have your help.
 
-## Code style
+## How to Contribute
+1. Fork the repository.
+2. Create a new branch for your feature or bug fix.
+3. Make your changes, and test them thoroughly.
+4. Commit your changes and push them to your fork.
+5. Submit a pull request to the main repository in [PR tab](https://github.com/EternalCodeTeam/EternalCore/compare).
 
-#### Try to stick with our code style. Browse files, and you will know what we actually mean. Keep in mind that we don't use '*' imports.
+## Code of Conduct
+We ask that all contributors adhere to our [code of conduct](./CODE_OF_CONDUCT.md). By participating in this project, you agree to abide by its terms.
 
-#### Also don't include the `.idea/` folder.
+## Reporting Issues
+If you find an issue with the plugin, please report it in the [Issues tab](https://github.com/EternalCodeTeam/EternalCore/issues/new/choose). Please provide as much information as possible, including the version of server software that you are using and the plugin you are using, as well as any error messages or logs.
 
-## Naming
+## Submitting a Pull Request
+When submitting a pull request, please make sure to follow these guidelines:
 
-#### Pull requests should be named like that:
+* Make sure that your code adheres to the plugin's existing coding style.
+* Test your changes thoroughly before submitting the pull request.
+* If your pull request is related to an existing issue, please reference the issue in your pull request.
+* Provide a detailed description of your changes and their motivation.
+* Include any relevant screenshots or demonstrations of the changes.
+* Make sure that your pull request passes all automated tests and code checks.
 
-`GH-{NUMBER} Title of PR`
+## License
+EternalCore is licensed under the [GPL-3.0](../LICENSE). By contributing to this project, you agree to license your contributions under the same terms.
 
-Please don't include troll, racist and sexual names. We are a mature project.
-
-## Building
-
-#### You can build EternalCore using `shadowJar` Gradle task or `./gradlew shadowJar` Command in GitBash.
-
-#### Output file will be located at `build/libs`
+Thank you for your interest in contributing to EternalCore!

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,5 +1,31 @@
-**Please describe the changes made by this PR and why they need to be merged:**
----
-**NOTE:** Remember to add all the necessary changes to the CHANGELOGS file
+## Description
+
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
+
+Fixes # (issue)
+
+## Type of change
+
+Please delete options that are not relevant.
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] This change requires a documentation update
+
+## How Has This Been Tested?
+
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
+
+- [ ] Test A
+- [ ] Test B
+
+## Checklist:
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have made corresponding changes to readme etc.
+- [ ] My changes generate no new warnings
+- [ ] I have added test to cover my changes
+- [ ] I have added appropriate labels to this Pull Request
 
-**Status:**

.github/auto_assign.yml

@@ -632,7 +632,7 @@ state the exclusion of warranty; and each file should have at least
 the "copyright" line and a pointer to where the full notice is found.
 
     <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
+    Copyright (C) 2022-2023  EternalCode
 
     This program is free software: you can redistribute it and/or modify
     it under the terms of the GNU General Public License as published by
@@ -652,7 +652,7 @@ Also add information on how to contact you by electronic and paper mail.
   If the program does terminal interaction, make it output a short
 notice like this when it starts in an interactive mode:
 
-    <program>  Copyright (C) <year>  <name of author>
+    Copyright (C) 2022-2023  EternalCode
     This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
     This is free software, and you are welcome to redistribute it
     under certain conditions; type `show c' for details.