patch v2.0.11-beta: fix env issue in GA release, warn Intel Mac users, add com templates. (#115)

* fix: throw error for Intel Mac user
* docs: first draft of issue and PR template
* fix: env of curseforge API key and discord client ID
This commit is contained in:
Fazri Gading
2026-01-23 21:30:27 +08:00
committed by GitHub
parent fc05725a43
commit 34143d9872
16 changed files with 688 additions and 0 deletions

View File

@@ -0,0 +1,24 @@
## Description
Brief description of the bug fix.
## Related Issue
Fixes # (issue number)
## Changes Made
- List the changes made to fix the bug
- Be specific about what was changed and why
## Testing
- How did you test the fix?
- What scenarios were covered?
## Screenshots (if applicable)
Add screenshots to demonstrate the fix.
## 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
- [ ] 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

View File

@@ -0,0 +1,16 @@
## Description
Brief description of the documentation changes.
## Related Issue
Addresses # (issue number)
## Changes Made
- List the documentation files that were added, updated, or removed
- Describe what information was added or corrected
## Checklist
- [ ] Documentation is clear and easy to understand
- [ ] Links and references are correct
- [ ] Code examples (if any) are accurate and functional
- [ ] Spelling and grammar are correct
- [ ] Documentation follows the project's style guidelines

26
.github/PULL_REQUEST_TEMPLATE/hotfix.md vendored Normal file
View File

@@ -0,0 +1,26 @@
## Description
Brief description of the hotfix.
## Related Issue
Fixes # (issue number) - URGENT
## Changes Made
- List the minimal changes made to fix the critical issue
- Be specific about what was changed
## Urgency
Why is this a hotfix? (Critical bug, security issue, production down, etc.)
## Testing
- How was the hotfix tested?
- What was the minimal testing performed?
## Deployment Notes
- Any special deployment considerations?
- Rollback plan if needed?
## Checklist
- [ ] This is a minimal change addressing only the critical issue
- [ ] No new features or unrelated changes included
- [ ] Basic functionality verified
- [ ] Ready for immediate deployment

View File

@@ -0,0 +1,20 @@
## Description
Brief description of the localization changes.
## Related Issue
Addresses # (issue number)
## Changes Made
- List the languages and files that were updated
- Describe what text was translated or updated
## Languages Updated
- Language 1 (locale code)
- Language 2 (locale code)
## Checklist
- [ ] Translations are accurate and culturally appropriate
- [ ] Placeholder variables (%s, %d, etc.) are preserved
- [ ] Text length is appropriate for UI elements
- [ ] No hardcoded strings remain
- [ ] Localization files are properly formatted

View File

@@ -0,0 +1,25 @@
## Description
Brief description of the new feature.
## Related Issue
Addresses # (issue number)
## Changes Made
- List the changes made to implement the feature
- Be specific about new files, modified files, and functionality added
## Testing
- How did you test the new feature?
- What scenarios were covered?
## Screenshots (if applicable)
Add screenshots to demonstrate the new feature.
## 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
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] I have updated the documentation accordingly

View File

@@ -0,0 +1,27 @@
## Description
Brief description of the refactoring changes.
## Related Issue
Addresses # (issue number)
## Changes Made
- List the refactored code sections
- Describe what was improved (readability, performance, maintainability, etc.)
## Motivation
Why was this refactoring necessary?
## Impact
- Does this change affect any APIs or interfaces?
- Are there any breaking changes?
## Testing
- How was the refactored code tested?
- Did existing tests pass?
## Checklist
- [ ] Code is more readable and maintainable
- [ ] No functionality was broken
- [ ] Performance was not negatively impacted
- [ ] All existing tests pass
- [ ] New tests were added if necessary