Adding the issue and pull rquest templates

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,43 @@
+---
+name: Bug Report
+about: Report a bug or technical issue
+title: "[BUG] "
+labels: ["bug"]
+assignees: []
+---
+
+## Bug Description
+<!-- A clear and concise description of what the bug is -->
+
+## Steps to Reproduce
+<!-- Steps to reproduce the behavior -->
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+## Expected Behavior
+<!-- A clear and concise description of what you expected to happen -->
+
+## Actual Behavior
+<!-- A clear and concise description of what actually happened -->
+
+## Environment
+- **OS**: 
+- **Browser**: 
+- **Version**: 
+
+## Additional Context
+<!-- Add any other context about the problem here -->
+
+## Screenshots
+<!-- If applicable, add screenshots to help explain your problem -->
+
+## Checklist
+- [ ] I have searched existing issues to avoid duplicates
+- [ ] I have provided clear steps to reproduce the issue
+- [ ] I have described the expected vs actual behavior
+- [ ] I have included relevant environment information
+
+---
+*This template helps us identify and fix bugs quickly. Thank you for your report!* 

.github/ISSUE_TEMPLATE/new-content-proposal.md

@@ -0,0 +1,65 @@
+---
+name: New Content Proposal
+about: Propose new problems, assignments, or course content
+title: "[NEW CONTENT] "
+labels: ["enhancement", "new-content"]
+assignees: []
+---
+
+## Content Type
+<!-- What type of new content are you proposing? -->
+- [ ] New problem
+- [ ] New assignment/section
+- [ ] Course improvement
+- [ ] Documentation update
+- [ ] Other: _________
+
+## Description
+<!-- Describe the new content you're proposing -->
+
+## Motivation
+<!-- Why is this content needed? How does it benefit the OMI course? -->
+
+## Content Details
+
+### For New Problems:
+- **Problem Title**: 
+- **Difficulty Level**: 
+  - [ ] Introductory
+  - [ ] Easy
+  - [ ] Medium
+  - [ ] Hard
+- **Topics Covered**: 
+- **Programming Languages**: 
+- **Estimated Time**: 
+
+### For New Assignments:
+- **Assignment Name**: 
+- **Description**: 
+- **Target Audience**: 
+- **Prerequisites**: 
+
+### For Course Improvements:
+- **Current State**: 
+- **Proposed Changes**: 
+- **Expected Benefits**: 
+
+## Implementation Plan
+<!-- How would you like to implement this? -->
+- [ ] I can provide the complete content
+- [ ] I can provide a partial implementation
+- [ ] I need help with implementation
+- [ ] I'm just proposing the idea
+
+## Additional Resources
+<!-- Any relevant links, references, or examples -->
+
+## Checklist
+- [ ] I have searched existing issues to avoid duplicates
+- [ ] I have provided a clear description of the proposed content
+- [ ] I have explained the motivation and benefits
+- [ ] I have specified the content type and details
+- [ ] I have indicated my implementation capabilities
+
+## Related Issues
+<!-- Link to any related issues or discussions -->

.github/ISSUE_TEMPLATE/typo-correction.md

@@ -0,0 +1,39 @@
+---
+name: Typo/Correction Issue
+about: Report a typo, error, or correction needed in course content
+title: "[Correction] "
+labels: ["typo", "correction"]
+assignees: []
+---
+
+## Description
+<!-- Describe the typo or error you found -->
+
+**Location**: 
+- [ ] Problem statement
+- [ ] Solution explanation
+- [ ] Test cases
+- [ ] Course description
+- [ ] Other: _________
+
+**File(s) affected**: 
+<!-- Specify the file path(s) where the issue is located -->
+
+## Current Content
+<!-- Copy the current incorrect content here -->
+
+## Suggested Correction
+<!-- Provide the corrected content -->
+
+## Additional Context
+<!-- Any additional information that might be helpful -->
+
+## Checklist
+- [ ] I have searched existing issues to avoid duplicates
+- [ ] I have provided the exact location of the issue
+- [ ] I have included the current incorrect content
+- [ ] I have provided a clear correction
+- [ ] I have checked that my correction is accurate
+
+## Screenshots (if applicable)
+<!-- Add screenshots if the issue is visual -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,56 @@
+## Description
+<!-- Provide a brief description of the changes made -->
+
+## Issue
+Fixes: #
+
+## Type of Change
+<!-- What type of change does your PR introduce? -->
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
+- [ ] Content addition/modification
+- [ ] Other: _________
+
+## Content Changes (if applicable)
+<!-- If this PR involves content changes, specify what was modified -->
+- [ ] Problem statement
+- [ ] Solution explanation
+- [ ] Test cases
+- [ ] Course structure
+- [ ] Documentation
+- [ ] Other: _________
+
+## Files Modified
+<!-- List the files that were modified -->
+- 
+
+## Testing
+<!-- How have you tested your changes? -->
+- [ ] I have tested the changes locally
+- [ ] I have verified that all test cases pass
+- [ ] I have checked that the content is accurate
+- [ ] I have reviewed the changes for typos/errors
+
+## Checklist
+<!-- Go over all the following points, and put an `x` in all the boxes that apply -->
+- [ ] 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
+- [ ] I have made corresponding changes to the documentation
+- [ ] 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
+- [ ] Any dependent changes have been merged and published in downstream modules
+
+## Additional Notes
+<!-- Add any other context about the pull request here -->
+
+## Screenshots (if applicable)
+<!-- Add screenshots if the changes are visual -->
+
+## Related Issues
+<!-- Link to any related issues -->
+
+