39 lines
1.3 KiB
Markdown
39 lines
1.3 KiB
Markdown
## Pull Request Checklist
|
||
|
||
- [ ] PR is targeting the `dev` branch
|
||
- [ ] I have pulled the latest changes from `dev` and resolved any merge conflicts
|
||
- [ ] My code follows the project’s style guidelines
|
||
- [ ] I have tested my changes and ensured they work as expected
|
||
- [ ] Relevant documentation/comments have been added or updated
|
||
- [ ] Any dependent changes have been merged
|
||
|
||
### Resource Relevance and Usage
|
||
- [ ] Resource is active on 100+ servers, OR
|
||
- [ ] Resource has a verifiable dependency on community_bridge, OR
|
||
- [ ] Exception justified (adds value or supports project goals)
|
||
|
||
### Avoiding Breaking Changes
|
||
- [ ] No breaking changes introduced, OR
|
||
- [ ] If deprecating: 2-4 month grace period provided
|
||
- [ ] Deprecation notices clearly documented in code with dates
|
||
|
||
### Documentation and Testing
|
||
- [ ] At least one usage example included.
|
||
- [ ] IntelliSense-style comments added.
|
||
- [ ] Unit test coverage provided
|
||
|
||
## Description
|
||
|
||
<!-- Please include a summary of the changes and the purpose of this PR -->
|
||
|
||
## Related Issues
|
||
|
||
<!-- If this PR addresses any issues, please link them here using "Fixes #issue_number" -->
|
||
|
||
## Testing Steps
|
||
|
||
<!-- Describe how the changes were tested and how reviewers can verify them -->
|
||
|
||
## Additional Notes
|
||
|
||
<!-- Add any other relevant information or context here --> |