Initial commit: Fresh start

- Removed all old commits

Author: VoxHash

.github/FUNDING.yml

@@ -0,0 +1,15 @@
+# These are supported funding model platforms
+
+github: [voxhash] # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: voxhash # Replace with a single Patreon username
+open_collective: voxhash # Replace with a single Open Collective username
+ko_fi: voxhash # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: voxhash # Replace with a single Liberapay username
+issuehunt: voxhash # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: voxhash # Replace with a single Buy Me a Coffee username
+thanks_dev: voxhash # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,46 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Environment (please complete the following information):**
+ - OS: [e.g. Windows 10, macOS 12, Ubuntu 20.04]
+ - Python version: [e.g. 3.10.0]
+ - Application version: [e.g. 1.0.0]
+ - Telegram API version: [e.g. 1.28.0]
+
+**Logs**
+Please include relevant log entries:
+
+```
+Paste log entries here
+```
+
+**Additional context**
+Add any other context about the problem here.
+
+**Checklist**
+- [ ] I have searched existing issues to avoid duplicates
+- [ ] I have checked the documentation
+- [ ] I have provided all required information
+- [ ] I have included relevant logs

.github/ISSUE_TEMPLATE/docs_improvement.md

@@ -0,0 +1,29 @@
+---
+name: Documentation improvement
+about: Suggest an improvement to the documentation
+title: '[DOCS] '
+labels: documentation
+assignees: ''
+---
+
+**What documentation needs improvement?**
+A clear description of which documentation section or file needs improvement.
+
+**Current state**
+Describe what the current documentation says or what's missing.
+
+**Proposed improvement**
+Describe what should be changed or added to improve the documentation.
+
+**Why is this improvement needed?**
+Explain why this documentation improvement would be helpful.
+
+**Additional context**
+Add any other context, examples, or screenshots about the documentation improvement here.
+
+**Checklist**
+- [ ] I have searched existing documentation issues to avoid duplicates
+- [ ] I have identified the specific documentation that needs improvement
+- [ ] I have provided a clear description of the proposed improvement
+- [ ] I have explained why this improvement is needed
+

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,35 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Use case**
+Describe the specific use case for this feature. How would it benefit users?
+
+**Implementation details**
+If you have ideas about how this feature could be implemented, please describe them.
+
+**Screenshots/Mockups**
+If applicable, add screenshots or mockups to help explain your feature request.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
+
+**Checklist**
+- [ ] I have searched existing feature requests to avoid duplicates
+- [ ] I have provided a clear use case
+- [ ] I have considered the implementation complexity
+- [ ] I have provided all required information

.github/pull_request_template.md

@@ -0,0 +1,53 @@
+## Description
+Brief description of the changes made.
+
+## Type of Change
+- [ ] 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)
+- [ ] Documentation update
+- [ ] Code refactoring
+- [ ] Performance improvement
+- [ ] Test coverage improvement
+
+## Related Issues
+Fixes #(issue number)
+Closes #(issue number)
+Related to #(issue number)
+
+## Changes Made
+- [ ] List the specific changes made
+- [ ] Include any new files added
+- [ ] Include any files modified
+- [ ] Include any files removed
+
+## Testing
+- [ ] Unit tests added/updated
+- [ ] Integration tests added/updated
+- [ ] Manual testing performed
+- [ ] All tests pass locally
+
+## Screenshots (if applicable)
+Add screenshots to help explain your changes.
+
+## Checklist
+- [ ] My code follows the project's style guidelines
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published
+
+## Additional Notes
+Any additional information that reviewers should know about this PR.
+
+## Breaking Changes
+If this is a breaking change, please describe the impact and migration path.
+
+## Performance Impact
+If this change affects performance, please describe the impact.
+
+## Security Considerations
+If this change affects security, please describe the considerations.