-
Notifications
You must be signed in to change notification settings - Fork 55
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
aa6102f
commit 2ace918
Showing
1 changed file
with
44 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
--- | ||
name: Changes in Code | ||
about: Issue for proposing changes in the codebase | ||
title: Code Changes | ||
labels: '' | ||
assignees: '' | ||
|
||
--- | ||
|
||
### Title of the Issue | ||
- [ ] **Have you named the issue title clearly and descriptively?** | ||
- [ ] **Have you searched for existing issues in the project to avoid duplicates?** | ||
<!-- Example: "refactor: [Component] Optimize search algorithm" --> | ||
<!-- Use format: "refactor: [affected section] concise description" --> | ||
|
||
### Description | ||
<!-- Provide a detailed description of the code change you're suggesting and why it's necessary. --> | ||
|
||
### Affected Sections (Code or Documentation) | ||
<!-- Specify which sections of the codebase or documentation will be affected by this change. --> | ||
|
||
- [ ] Code | ||
- [ ] Documentation | ||
|
||
### Impact Analysis | ||
<!-- Describe the impact of this change on the project, including possible side effects and necessary modifications in the related modules or components. --> | ||
|
||
### Steps to Reproduce (if applicable) | ||
<!-- Provide a step-by-step description of how to reproduce the issue or verify the changes. --> | ||
|
||
### Additional Context | ||
<!-- Add any other context or screenshots about the issue here. --> | ||
|
||
### Checklist | ||
- [ ] I have followed the issue title guidelines. | ||
- [ ] I have categorized the change as code or documentation. | ||
- [ ] I have included a clear and detailed description of the change. | ||
- [ ] I have specified the affected sections. | ||
- [ ] I have provided an impact analysis. | ||
- [ ] I have included steps to reproduce (if applicable). | ||
- [ ] I have added any additional context or screenshots (if applicable). | ||
- [ ] I am a GSSOC contributor. | ||
- [ ] I have read and understood the GSSOC guidelines. | ||
- [ ] I have adhered to the code of conduct. |