Fix#3 : Implement Firebase authentication with domain validation

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,50 @@
+name: 🐛 Bug report
+description: Report a reproducible bug so we can fix it.
+title: "[BUG] "
+labels: ["bug"]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report an issue! Please fill in as much detail as you can.
+
+  - id: os
+    type: dropdown
+    attributes:
+      label: **Platform**
+      options:
+        - Windows
+        - macOS
+        - Linux
+        - Other
+
+  - id: version
+    type: input
+    attributes:
+      label: **Exam Bud version**
+      placeholder: e.g. `1.0.0`
+
+  - id: steps
+    type: textarea
+    attributes:
+      label: **Steps to reproduce**
+      description: Describe step-by-step how to trigger the bug.
+    validations:
+      required: true
+
+  - id: expected
+    type: textarea
+    attributes:
+      label: **Expected behavior**
+
+  - id: actual
+    type: textarea
+    attributes:
+      label: **What actually happened**
+
+  - id: logs
+    type: textarea
+    attributes:
+      label: **Logs / Screenshots**
+      description: Paste console output or screenshots if available.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,29 @@
+name: ✨ Feature request
+description: Suggest an enhancement or new feature.
+title: "[FEATURE] "
+labels: ["enhancement"]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for your suggestion! Please give us enough context to understand the need.
+
+  - id: summary
+    type: input
+    attributes:
+      label: **Brief summary**
+    validations:
+      required: true
+
+  - id: motivation
+    type: textarea
+    attributes:
+      label: **Motivation**
+      description: Why is this feature important?
+
+  - id: design
+    type: textarea
+    attributes:
+      label: **Proposed design**
+      description: How would you implement this?

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,23 @@
+# Description
+
+Please include a summary of the change and which issue is fixed.  
+Fixes # (issue number)
+
+## Type of change
+
+- [ ] Bug fix (non-breaking change)
+- [ ] New feature (non-breaking change)
+- [ ] Breaking change
+- [ ] Documentation update
+
+## Proof of Work (Screenshots or Video) if applicable
+
+Please include proper screenshots and proof of work depicting the changes. 
+
+## Checklist
+
+- [ ] My code follows the project’s style guidelines
+- [ ] I have performed a self-review of my own code
+- [ ] I’ve commented my code, particularly in hard-to-understand areas
+- [ ] I have added tests that prove my fix is effective or my feature works
+- [ ] I have added necessary documentation (if appropriate)

.github/workflows/ci.yml

@@ -0,0 +1,39 @@
+name: CI – Docker & Node Checks
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  docker-build:
+    name: Build Docker Images
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: docker/setup-buildx-action@v2
+      - run: docker build ./backend  -t exam-bud-backend:ci
+      - run: docker build ./frontend -t exam-bud-frontend:ci
+
+  node-checks:
+    name: 🔧 Install & Build in Node
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        service: [ backend, frontend ]
+    defaults:
+      run:
+        working-directory: ${{ matrix.service }}
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 18
+      - run: npm ci
+      - run: |
+          if [ "${{ matrix.service }}" = "frontend" ]; then
+            npm run build
+          else
+            npx prisma generate
+          fi

.github/workflows/commitlint.yml

@@ -0,0 +1,42 @@
+name:  Commit & PR Title Lint
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  commitlint:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout full history
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+
+      - name: Lint commit messages & PR title
+        uses: wagoid/commitlint-github-action@v4
+        with:
+          config: |
+            extends:
+              - "@commitlint/config-conventional"
+            rules:
+              type-enum:
+                - 2
+                - always
+                - [
+                    "feat",
+                    "fix",
+                    "docs",
+                    "style",
+                    "refactor",
+                    "test",
+                    "chore",
+                    "ci",
+                    "build",
+                    "perf"
+                  ]
+          titleAndCommits: true
+          allowMergeCommits: true
+          github_token: ${{ secrets.GITHUB_TOKEN }}

CONTRIBUTING.md

@@ -26,8 +26,8 @@ If you’re unsure about something or need help getting started:
 
 That's okay — everyone starts somewhere! 😊  
 Start by learning the basics:
-- [Git & GitHub Crash Course](https://www.youtube.com/watch?v=RGOj5yH7evk)
 - [Doc to help you get started](https://medium.com/@ritankar.saha786/understanding-git-and-github-b79bb84de9e8) for terms like fork, pull request, branch, etc.
+- [Git & GitHub Crash Course](https://www.youtube.com/watch?v=RGOj5yH7evk)
 
 ---
 
@@ -37,7 +37,7 @@ Awesome! 🎉 Let’s walk you through:
 - Check out the [open issues](https://github.com/bsoc-bitbyte/ExamBud/issues).
 - Look for issues labeled [`good first issue`](https://github.com/bsoc-bitbyte/ExamBud/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22).
 - Comment on an issue you'd like to work on and ask to be assigned.
-- Follow this [pull request tutorial](https://medium.com/@ritankar.saha786/understanding-git-and-github-b79bb84de9e8) to make your first PR.
+- Follow this [pull request tutorial blog](https://medium.com/@ritankar.saha786/understanding-git-and-github-b79bb84de9e8) to make your first PR.
 
 Feel free to ask questions in the issue or on Discord if you're stuck.
 
@@ -77,6 +77,7 @@ Keep your code clean and consistent:
 - Keep indentation and formatting consistent with the codebase.
 - Write clear and concise comments when needed.
 - Follow any existing patterns already in the code.
+- More about this will be discussed in the session, be sure to join that
 
 If you're unsure about style, check how other parts of the code are written and follow suit.
 
@@ -106,15 +107,18 @@ We follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0
 ```
 feat(ui): add dark-mode
 feat(fix): fixed the backend logic
+feat: did this
+fix: fixed that
 ```
-
+We wont't be very strict with this but nice to write proper commit messages.
 ---
 
 ### Before making a PR
 
 Read: [How to make a pull request](https://medium.com/@ritankar.saha786/understanding-git-and-github-b79bb84de9e8)  -- Scroll Down to the Bottom. 
 Make sure:
 - Your code is tested (if applicable)
+- Attach Screenshots and Videos if applicable
 - Follows the style guide
 - Follows commit message rules
 - Issue is linked or referenced
@@ -126,5 +130,5 @@ See you in the PRs! 🎉
 
 Maintainers 
 
-Ritankar Saha
-Harshil Khandelwal
+[Ritankar Saha](https://github.com/ritankarsaha)
+[Harshil Khandelwal]()