Skip to content

Commit 3b7b8bb

Browse files
committed
Release v1.2.0: Enhanced stability, spintax processing, settings persistence, and comprehensive platform support
1 parent 1abf716 commit 3b7b8bb

74 files changed

Lines changed: 19903 additions & 1440 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Lines changed: 23 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,44 +1,46 @@
11
---
2-
name: 🐛 Bug Report
3-
about: Create a report to help us improve the application
2+
name: Bug report
3+
about: Create a report to help us improve
44
title: '[BUG] '
5-
labels: ['bug', 'needs-triage']
5+
labels: bug
66
assignees: ''
77

88
---
99

10-
## 🐛 Bug Description
10+
**Describe the bug**
1111
A clear and concise description of what the bug is.
1212

13-
## 🔄 Steps to Reproduce
13+
**To Reproduce**
1414
Steps to reproduce the behavior:
1515
1. Go to '...'
1616
2. Click on '....'
1717
3. Scroll down to '....'
1818
4. See error
1919

20-
## 🎯 Expected Behavior
20+
**Expected behavior**
2121
A clear and concise description of what you expected to happen.
2222

23-
## 📱 Screenshots
23+
**Screenshots**
2424
If applicable, add screenshots to help explain your problem.
2525

26-
## 🖥️ Environment
27-
- **OS**: [e.g. Windows 10, macOS 12.0, Ubuntu 20.04]
28-
- **Python Version**: [e.g. 3.10.0]
29-
- **Application Version**: [e.g. 1.0.0]
30-
- **PyQt5 Version**: [e.g. 5.15.0]
26+
**Environment (please complete the following information):**
27+
- OS: [e.g. Windows 10, macOS 12, Ubuntu 20.04]
28+
- Python version: [e.g. 3.10.0]
29+
- Application version: [e.g. 1.0.0]
30+
- Telegram API version: [e.g. 1.28.0]
3131

32-
## 📋 Additional Context
33-
Add any other context about the problem here.
32+
**Logs**
33+
Please include relevant log entries:
3434

35-
## 🔍 Error Logs
3635
```
37-
Paste any relevant error logs here
36+
Paste log entries here
3837
```
3938

40-
## ✅ Checklist
41-
- [ ] I have searched for existing issues before creating this one
42-
- [ ] I have provided all the requested information
43-
- [ ] I have tested this on the latest version
44-
- [ ] I have included error logs if applicable
39+
**Additional context**
40+
Add any other context about the problem here.
41+
42+
**Checklist**
43+
- [ ] I have searched existing issues to avoid duplicates
44+
- [ ] I have checked the documentation
45+
- [ ] I have provided all required information
46+
- [ ] I have included relevant logs
Lines changed: 23 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -1,46 +1,35 @@
11
---
2-
name: Feature Request
2+
name: Feature request
33
about: Suggest an idea for this project
44
title: '[FEATURE] '
5-
labels: ['enhancement', 'needs-triage']
5+
labels: enhancement
66
assignees: ''
77

88
---
99

10-
## 🚀 Feature Description
11-
A clear and concise description of the feature you'd like to see implemented.
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
1212

13-
## 💡 Use Case
14-
Describe the problem this feature would solve or the use case it would enable.
15-
16-
## 🎯 Proposed Solution
13+
**Describe the solution you'd like**
1714
A clear and concise description of what you want to happen.
1815

19-
## 🔄 Alternative Solutions
16+
**Describe alternatives you've considered**
2017
A clear and concise description of any alternative solutions or features you've considered.
2118

22-
## 📱 Mockups/Examples
23-
If applicable, add mockups, screenshots, or examples to help explain your feature.
24-
25-
## 🎨 UI/UX Considerations
26-
- How should this feature be accessed?
27-
- What should the user interface look like?
28-
- Any specific design requirements?
29-
30-
## 🔧 Technical Considerations
31-
- Any specific technical requirements?
32-
- Dependencies or integrations needed?
33-
- Performance considerations?
34-
35-
## 📊 Priority
36-
- [ ] Low - Nice to have
37-
- [ ] Medium - Would improve the application
38-
- [ ] High - Critical for my use case
39-
- [ ] Urgent - Blocking my workflow
40-
41-
## ✅ Checklist
42-
- [ ] I have searched for existing feature requests before creating this one
43-
- [ ] I have provided a clear description of the feature
44-
- [ ] I have explained the use case and benefits
45-
- [ ] I have considered alternative solutions
46-
- [ ] I have provided any relevant mockups or examples
19+
**Use case**
20+
Describe the specific use case for this feature. How would it benefit users?
21+
22+
**Implementation details**
23+
If you have ideas about how this feature could be implemented, please describe them.
24+
25+
**Screenshots/Mockups**
26+
If applicable, add screenshots or mockups to help explain your feature request.
27+
28+
**Additional context**
29+
Add any other context or screenshots about the feature request here.
30+
31+
**Checklist**
32+
- [ ] I have searched existing feature requests to avoid duplicates
33+
- [ ] I have provided a clear use case
34+
- [ ] I have considered the implementation complexity
35+
- [ ] I have provided all required information

.github/pull_request_template.md

Lines changed: 39 additions & 51 deletions
Original file line numberDiff line numberDiff line change
@@ -1,65 +1,53 @@
1-
## 📝 Description
2-
A clear and concise description of what this PR does.
3-
4-
## 🔗 Related Issues
5-
- Closes #(issue number)
6-
- Related to #(issue number)
7-
8-
## 🎯 Type of Change
9-
- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
10-
- [ ] ✨ New feature (non-breaking change which adds functionality)
11-
- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
12-
- [ ] 📚 Documentation update
13-
- [ ] 🎨 Code style/formatting changes
14-
- [ ] ♻️ Code refactoring
15-
- [ ] ⚡ Performance improvements
16-
- [ ] 🧪 Test additions or updates
17-
18-
## 🧪 Testing
19-
- [ ] I have tested this change locally
20-
- [ ] I have added tests that prove my fix is effective or that my feature works
21-
- [ ] New and existing unit tests pass locally with my changes
22-
- [ ] I have tested the GUI functionality
23-
- [ ] I have tested database operations
24-
- [ ] I have tested the Telegram integration (if applicable)
25-
26-
## 📱 Screenshots (if applicable)
1+
## Description
2+
Brief description of the changes made.
3+
4+
## Type of Change
5+
- [ ] Bug fix (non-breaking change which fixes an issue)
6+
- [ ] New feature (non-breaking change which adds functionality)
7+
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
8+
- [ ] Documentation update
9+
- [ ] Code refactoring
10+
- [ ] Performance improvement
11+
- [ ] Test coverage improvement
12+
13+
## Related Issues
14+
Fixes #(issue number)
15+
Closes #(issue number)
16+
Related to #(issue number)
17+
18+
## Changes Made
19+
- [ ] List the specific changes made
20+
- [ ] Include any new files added
21+
- [ ] Include any files modified
22+
- [ ] Include any files removed
23+
24+
## Testing
25+
- [ ] Unit tests added/updated
26+
- [ ] Integration tests added/updated
27+
- [ ] Manual testing performed
28+
- [ ] All tests pass locally
29+
30+
## Screenshots (if applicable)
2731
Add screenshots to help explain your changes.
2832

29-
## 🔍 Code Quality
33+
## Checklist
3034
- [ ] My code follows the project's style guidelines
3135
- [ ] I have performed a self-review of my own code
3236
- [ ] I have commented my code, particularly in hard-to-understand areas
3337
- [ ] I have made corresponding changes to the documentation
3438
- [ ] My changes generate no new warnings
3539
- [ ] I have added tests that prove my fix is effective or that my feature works
36-
37-
## 📋 Checklist
38-
- [ ] My code follows the project's coding standards
39-
- [ ] I have performed a self-review of my own code
40-
- [ ] I have commented my code, particularly in hard-to-understand areas
41-
- [ ] I have made corresponding changes to the documentation
42-
- [ ] My changes generate no new warnings
43-
- [ ] I have added tests that prove my fix is effective or that my feature works
4440
- [ ] New and existing unit tests pass locally with my changes
4541
- [ ] Any dependent changes have been merged and published
4642

47-
## 🚀 Deployment Notes
48-
Any special deployment considerations or notes for reviewers.
43+
## Additional Notes
44+
Any additional information that reviewers should know about this PR.
4945

50-
## 📚 Documentation
51-
- [ ] I have updated the README if needed
52-
- [ ] I have updated the CHANGELOG if needed
53-
- [ ] I have updated any relevant documentation
54-
- [ ] I have added/updated docstrings for new functions/classes
46+
## Breaking Changes
47+
If this is a breaking change, please describe the impact and migration path.
5548

56-
## 🔒 Security
57-
- [ ] My changes don't introduce any security vulnerabilities
58-
- [ ] I have considered the security implications of my changes
59-
- [ ] I have not hardcoded any sensitive information
49+
## Performance Impact
50+
If this change affects performance, please describe the impact.
6051

61-
## 🎨 UI/UX
62-
- [ ] My changes maintain the existing UI/UX consistency
63-
- [ ] I have tested the changes on different screen sizes
64-
- [ ] I have considered accessibility implications
65-
- [ ] The changes are intuitive and user-friendly
52+
## Security Considerations
53+
If this change affects security, please describe the considerations.

0 commit comments

Comments
 (0)