Enhance PR template: friendlier, more detailed, human-readable

Author: Rehaxl

.github/pull_request_template.md

@@ -1,21 +1,68 @@
-### Describe your change:
-
-
-
-* [ ] Add an algorithm?
-* [ ] Fix a bug or typo in an existing algorithm?
-* [ ] Add or change doctests? -- Note: Please avoid changing both code and tests in a single pull request.
-* [ ] Documentation change?
-
-### Checklist:
-* [ ] I have read [CONTRIBUTING.md](https://github.com/TheAlgorithms/Python/blob/master/CONTRIBUTING.md).
-* [ ] This pull request is all my own work -- I have not plagiarized.
-* [ ] I know that pull requests will not be merged if they fail the automated tests.
-* [ ] This PR only changes one algorithm file.  To ease review, please open separate PRs for separate algorithms.
-* [ ] All new Python files are placed inside an existing directory.
-* [ ] All filenames are in all lowercase characters with no spaces or dashes.
-* [ ] All functions and variable names follow Python naming conventions.
-* [ ] All function parameters and return values are annotated with Python [type hints](https://docs.python.org/3/library/typing.html).
-* [ ] All functions have [doctests](https://docs.python.org/3/library/doctest.html) that pass the automated testing.
-* [ ] All new algorithms include at least one URL that points to Wikipedia or another similar explanation.
-* [ ] If this pull request resolves one or more open issues then the description above includes the issue number(s) with a [closing keyword](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue): "Fixes #ISSUE-NUMBER".
+## 📝 Description of Changes
+
+Hello! 👋 Please provide a detailed description of what your pull request does.  
+Explain the problem you’re solving, the motivation behind your changes, and any context that might help the maintainers understand your work.
+
+For example:
+- What issue or bug does this PR address?  
+- Why is this change important or helpful?  
+- Are there any design decisions or trade-offs to note?
+
+Fixes #(issue number) if applicable.
+
+---
+
+## 🌟 Motivation & Context
+
+Give a little background to help reviewers understand your thought process.  
+This is your chance to explain *why* you approached the problem the way you did.  
+
+For example:
+- Did you find a more efficient solution?  
+- Are you adding new functionality that didn’t exist before?  
+- Did you improve documentation, readability, or testing?
+
+---
+
+## 📸 Screenshots / Output (if applicable)
+
+If your PR changes visuals, algorithm output, or logs, please add screenshots, gifs, or text samples here.  
+This makes it easier for maintainers to review and understand your work.
+
+---
+
+## ✅ Type of Change
+
+Please select one or more options that apply:
+
+- [ ] 🐛 Bug fix – Non-breaking change that fixes an issue  
+- [ ] ✨ New feature – Adds new functionality  
+- [ ] ⚡ Enhancement / Refactor – Improves or optimizes existing code  
+- [ ] 📝 Documentation update – Improves instructions, examples, or guides  
+
+---
+
+## 📋 Checklist
+
+Before submitting your PR, please check off the following:
+
+- [ ] I have read and understood the [CONTRIBUTING.md](CONTRIBUTING.md) guide  
+- [ ] This PR is my own work and not copied from elsewhere  
+- [ ] My code follows the project’s coding style, naming conventions, and best practices  
+- [ ] I have added or updated tests/doctests where necessary  
+- [ ] All automated tests, linting, and formatting pass successfully  
+- [ ] I have added links or references to relevant issues, documentation, or sources  
+- [ ] I have provided screenshots, output, or examples if applicable  
+- [ ] I have explained the motivation and context clearly above  
+
+---
+
+## 🔗 Related Issues / References
+
+List any related issues, discussions, or external references here.  
+Use the GitHub closing keywords if your PR resolves issues automatically (e.g., `Fixes #123`).
+
+---
+
+💡 **Tip for contributors:**  
+Try to make your PR description as clear as possible. Imagine you’re explaining your changes to someone seeing the project for the first time — this helps maintainers review faster and increases the chances your PR will be merged smoothly.