Test PR to test Greet Contributor Workflow

.github/ISSUE_TEMPLATE/configuration_change.yml

@@ -0,0 +1,39 @@
+name: ⚙️ Configuration Change
+description: Suggest modifications to the project’s configuration, such as build tools, CI/CD pipeline adjustments, or environment settings to improve project management or deployment.
+
+body:
+  - type: textarea
+    id: configuration-change
+    attributes:
+      label: ⚙️ The Configuration Change
+      description: >
+        Describe the specific configuration change you propose. What configuration settings or tools need adjustment?
+        Mention which part of the project this affects, like build tools, CI/CD settings, or deployment configurations.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Motivation, pitch
+      description: >
+        Explain the reason for this configuration change. How will it improve the project's management or deployment process?
+        For example, will it streamline the CI/CD pipeline, improve build times, or make the project easier to maintain?
+    validations:
+      required: true
+
+  - type: checkboxes
+    attributes:
+      label: Configuration Change Focus Areas
+      options:
+        - "Build tools"
+        - "CI/CD pipeline"
+        - "Environment settings"
+        - "Dependency management"
+        - "Other"
+    validations:
+      required: false
+
+  - type: markdown
+    attributes:
+      value: >
+        Thank you for your contribution! 🔧 Please provide as much information as possible about the configuration change and how it will benefit the project.

.github/ISSUE_TEMPLATE/re-implementation.yml

@@ -0,0 +1,40 @@
+name: 🔄 Re-Implementation
+description: Suggest rewriting or replacing a part of the codebase for better performance, maintainability, or functionality.
+
+body:
+  - type: textarea
+    id: re-implementation
+    attributes:
+      label: 🔄 The re-implementation
+      description: >
+        A clear and concise description of the part of the system that you think needs re-implementation. 
+        What specific functionality or code block would you like to rewrite or replace? Please explain the issue in detail.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Motivation, pitch
+      description: >
+        Please provide the motivation for re-implementing this part of the code. 
+        Why do you think the current implementation needs to be replaced or rewritten? 
+        E.g., *"The current implementation is slow, hard to maintain, or outdated."* If you have any supporting context or examples, please include them here.
+    validations:
+      required: true
+
+  - type: checkboxes
+    attributes:
+      label: Areas of Focus
+      options:
+        - "Performance"
+        - "Maintainability"
+        - "Code readability"
+        - "Functionality improvement"
+        - "Other"
+    validations:
+      required: false
+
+  - type: markdown
+    attributes:
+      value: >
+        Thanks for contributing 🎉! Be as detailed as you can in your suggestion. The more information you provide, the easier it will be to understand the need for re-implementation and how it can improve the project!

.github/ISSUE_TEMPLATE/refactor-to-enhance.yml

@@ -0,0 +1,40 @@
+name: 🔧 Refactor to Enhance
+description: Suggest a refactor to improve the code's efficiency, readability, or maintainability while keeping its functionality intact.
+
+body:
+  - type: textarea
+    id: refactor-to-enhance
+    attributes:
+      label: 🔧 The refactor
+      description: >
+        Describe the part of the code that you think needs refactoring. What is the current problem or area that could benefit from enhancement? 
+        How do you think refactoring will improve the codebase?
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Motivation, pitch
+      description: >
+        Please explain the motivation for this refactor. Why is this refactor needed? 
+        What benefits will it bring to the codebase, such as improved performance, easier maintenance, or better readability?
+        Provide examples of how the code can be improved if possible.
+    validations:
+      required: true
+
+  - type: checkboxes
+    attributes:
+      label: Refactoring Focus Areas
+      options:
+        - "Performance"
+        - "Code readability"
+        - "Maintainability"
+        - "Reducing complexity"
+        - "Other"
+    validations:
+      required: false
+
+  - type: markdown
+    attributes:
+      value: >
+        Thank you for suggesting a refactor! 🎉 Be sure to provide as much detail as possible, and help the team understand how the refactor can improve the codebase!

.github/ISSUE_TEMPLATE/security_improvement.yml

@@ -0,0 +1,39 @@
+name: 🔒 Security Improvement
+description: Suggest changes to improve the project's security, including identifying vulnerabilities and proposing measures to harden the codebase.
+
+body:
+  - type: textarea
+    id: security-improvement
+    attributes:
+      label: 🔒 The Security Improvement
+      description: >
+        Describe the security improvement you propose. Identify any potential risks or vulnerabilities in the current setup
+        and detail the changes required to enhance security. Specify whether it impacts data handling, user authentication, or any external dependencies.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Motivation, pitch
+      description: >
+        Explain the motivation behind this security improvement. How does it protect against security risks, and what kind of
+        vulnerabilities does it address? Describe how it can prevent unauthorized access, data breaches, or other threats.
+    validations:
+      required: true
+
+  - type: checkboxes
+    attributes:
+      label: Security Improvement Focus Areas
+      options:
+        - "Data protection"
+        - "User authentication"
+        - "Dependency vulnerabilities"
+        - "Access control"
+        - "Other"
+    validations:
+      required: false
+
+  - type: markdown
+    attributes:
+      value: >
+        Thank you for prioritizing security! 🔒 Be as thorough as possible in identifying potential risks and detailing how your proposal will safeguard the project.

.github/workflows/build_and_deploy.yml

@@ -0,0 +1,82 @@
+name: Build and Deploy
+
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+    types: [closed]
+    branches:
+      - master
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      # 1. Remove Cached Flutter Installation
+      - name: Remove Cached Flutter Installation
+        run: rm -rf $HOME/.flutter
+
+      - name: Clean up old build files
+        run: |
+         rm -rf build/app/outputs/bundle/release/*
+
+      # 2. Checkout repository
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      # 3. Install Flutter SDK
+      - name: Install Flutter
+        uses: subosito/flutter-action@v2
+        with:
+          flutter-version: 3.27.2
+
+      # 4. Verify Flutter and Dart Versions
+      - name: Verify Flutter Installation
+        run: |
+          flutter --version
+          dart --version
+
+      # 6. Install Flutter dependencies
+      - name: Install Flutter Dependencies
+        run: flutter pub get
+
+      # 7. Build Android APK
+      - name: Build Android App Bundle
+        run: flutter build apk --release --split-per-abi
+
+      # 8. Upload build artifacts
+      - name: Upload APK as an artifact
+        uses: actions/upload-artifact@v4
+        with:
+            name: app-release-apks
+            path: build/app/outputs/apk/release/*.apk 
+
+  release:
+    runs-on: ubuntu-latest
+    needs: build
+    permissions:
+      contents: write
+    steps:
+      # 1. Checkout repository
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      # 2. Download build artifacts
+      - name: Download APK
+        uses: actions/download-artifact@v4
+        with:
+          name: app-release-apks
+          path: build/app/outputs/bundle/release/
+
+      # 3. Upload to Github Release
+      - name: Github Release
+        uses: ncipollo/[email protected]
+        with:
+          allowUpdates: true
+          artifacts: build/app/outputs/bundle/release/*.apk
+          artifactContentType: apk
+          generateReleaseNotes: true
+          tag: latest_build

.github/workflows/greet_contributors.yml

@@ -2,9 +2,9 @@ name: Greet Contributors
 
 on:
   issues:
-    types: [opened]
-  pull_request:
-    types: [opened]
+    types: [opened, closed]
+  pull_request_target:
+    types: [opened, closed]
 
 permissions:
   issues: write
@@ -16,34 +16,66 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - name: Print GitHub context
-        run: echo "${{ toJson(github) }}"
+      - name: Handle Opened Issues
+        if: github.event_name == 'issues' && github.event.action == 'opened'
+        uses: peter-evans/create-or-update-comment@v4
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          body: |
+            👋 **Hello @${{ github.actor }}!**  
+            Thank you for opening this issue. Our team will review it soon. 🚀  
+            - If you can, please provide more details like steps to reproduce, expected vs. actual behavior, and screenshots (if applicable). 📌  
+
+            We appreciate your contribution! 💡
+          reactions: heart
+
+      - name: Handle Closed Issues
+        if: github.event_name == 'issues' && github.event.action == 'closed'
+        uses: peter-evans/create-or-update-comment@v4
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          body: |
+            🔒 **Issue Closed - Thank You, @${{ github.actor }}!**  
+            This issue has been resolved or is no longer relevant.  
+            - If you have further questions, feel free to open a new issue. 💡  
 
-      - name: Send greeting message for issues
-        if: github.event_name == 'issues'
-        uses: actions-ecosystem/[email protected]
-        continue-on-error: true
+            Thanks for helping improve the project! 🚀
+          reactions: |
+            heart
+            hooray
+
+      - name: Handle Opened PRs
+        if: github.event_name == 'pull_request_target' && github.event.action == 'opened'
+        uses: peter-evans/create-or-update-comment@v4
         with:
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          repo: ${{ github.repository }}
-          number: ${{ github.event.issue.number }}
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.pull_request.number }}
           body: |
-            Hi @${{ github.event.issue.user.login }}!
-            Thanks for opening this issue, would you like to work on this?
+            🎉 **Welcome @${{ github.actor }}!**  
+            Thank you for your pull request! Our team will review it soon. 🔍  
+            - Please ensure your PR follows the contribution guidelines. ✅  
+            - All automated tests should pass before merging. 🔄  
+            - If this PR fixes an issue, link it in the description. 🔗  
+
+            We appreciate your contribution! 🚀
+          reactions: |
+            heart
 
-      - name: Send greeting message for PRs
-        if: github.event_name == 'pull_request'
-        uses: actions-ecosystem/[email protected]
-        continue-on-error: true
+      - name: Handle Closed PRs
+        if: github.event_name == 'pull_request_target' && github.event.action == 'closed'
+        uses: peter-evans/create-or-update-comment@v4
         with:
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          repo: ${{ github.repository }}
-          number: ${{ github.event.pull_request.number }}
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.pull_request.number }}
           body: |
-            Hi @${{ github.event.pull_request.user.login }}! 🎉
-            Thanks for opening this pull request. We appreciate your contribution.
+            ✅ **PR Closed - Thank You, @${{ github.actor }}!**  
+            - If this PR was merged: **Congratulations! Your contribution is now part of the project.** 🚀  
+            - If this PR was closed without merging: **Don’t worry! You can always improve it and submit again.** 💪  
 
-      - name: Log completion
-        run: |
-          echo "Greeting workflow completed successfully"
-          echo "Event type: ${{ github.event_name }}"
+            We appreciate your effort and look forward to more contributions from you! 🤝
+          reactions: |
+            heart
+            hooray 
+            rocket

.github/workflows/update-project-structure.yml

@@ -0,0 +1,31 @@
+name: Update Project Structure
+
+on:
+  push:
+    branches:
+      - github-action-project-structure
+      - dev
+
+jobs:
+  generate-structure:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Generate project structure
+        run: |
+          tree -a -I 'node_modules|.git' > project_structure.txt
+
+      - name: Commit and push changes
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+          if [[ -n $(git status --porcelain) ]]; then
+            git add project_structure.txt
+            git commit -m "chore: update project structure"
+            git push
+          else
+            echo "No changes to commit."
+          fi