@@ -39,32 +39,6 @@ Before creating bug reports, please check the [existing issues](https://github.c
3939- ** Include your environment details** (OS, Go version, Node version, Docker version, etc.)
4040- ** Include relevant logs or error messages**
4141
42- ** Bug Report Template:**
43- ``` markdown
44- ** Description:**
45- A clear and concise description of the bug.
46-
47- ** Steps to Reproduce:**
48- 1 . Go to '...'
49- 2 . Click on '...'
50- 3 . See error
51-
52- ** Expected Behavior:**
53- What you expected to happen.
54-
55- ** Actual Behavior:**
56- What actually happened.
57-
58- ** Environment:**
59- - OS: [ e.g., Ubuntu 22.04]
60- - Go Version: [ e.g., 1.25.4]
61- - Node Version: [ e.g., 20.x]
62- - Docker Version: [ e.g., 24.x]
63-
64- ** Additional Context:**
65- Add any other context, screenshots, or logs.
66- ```
67-
6842### Suggesting Enhancements
6943
7044Enhancement suggestions are tracked as GitHub issues. When creating an enhancement suggestion:
@@ -374,37 +348,6 @@ test(api): add integration tests for channel service
3743485 . ** Request review** from maintainers
3753496 . ** Address feedback** promptly and professionally
376350
377- ### Pull Request Template
378-
379- ``` markdown
380- ## Description
381- Brief description of what this PR does.
382-
383- ## Type of Change
384- - [ ] Bug fix (non-breaking change which fixes an issue)
385- - [ ] New feature (non-breaking change which adds functionality)
386- - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
387- - [ ] Documentation update
388-
389- ## Related Issue
390- Closes #(issue number)
391-
392- ## How Has This Been Tested?
393- Describe the tests you ran and how to reproduce them.
394-
395- ## Screenshots (if applicable)
396- Add screenshots to help explain your changes.
397-
398- ## Checklist
399- - [ ] My code follows the style guidelines of this project
400- - [ ] I have performed a self-review of my own code
401- - [ ] I have commented my code, particularly in hard-to-understand areas
402- - [ ] I have made corresponding changes to the documentation
403- - [ ] My changes generate no new warnings
404- - [ ] I have added tests that prove my fix is effective or that my feature works
405- - [ ] New and existing unit tests pass locally with my changes
406- ```
407-
408351### Review Process
409352
410353- Maintainers will review your PR as soon as possible
0 commit comments