Merge pull request #335 from EducationalTools/main

updates, add some gmaes, features and analytics

Author: ingoau

.coderabbit.yaml

@@ -0,0 +1,18 @@
+# yaml-language-server: $schema=https://storage.googleapis.com/coderabbit_public_assets/schema.v2.json
+enable_free_tier: true
+reviews:
+  review_status: true
+  poem: false
+  profile: chill
+  path_instructions:
+    - path: '**/*.*'
+      instructions: |
+        Do not correct spelling errors or grammar mistakes.
+  auto_review:
+    enabled: true
+    base_branches:
+      - main
+      - prod
+  tools:
+    languagetool:
+      enabled: false

.github/dependabot.yml

@@ -8,6 +8,4 @@ updates:
   - package-ecosystem: 'npm' # See documentation for possible values
     directory: '/' # Location of package manifests
     schedule:
-      interval: 'daily'
-    assignees:
-      - Inglan
+      interval: 'weekly'

.github/workflows/production_deploy.yml

@@ -0,0 +1,32 @@
+name: 'Move Project Items to Production'
+
+on:
+  push:
+    branches:
+      - prod
+
+jobs:
+  move_to_production:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.13'
+      - uses: actions/create-github-app-token@v1
+        id: app-token
+        with:
+          app-id: ${{ secrets.GH_APP_ID }}
+          private-key: ${{ secrets.GH_PRIVATE_KEY }}
+      - name: Install dependencies
+        run: |
+          python -m venv venv
+          venv/bin/pip install requests
+      - name: Move items from Done to In Production
+        run: |
+          venv/bin/python ci/scripts/move_to_production.py \
+            -t ${{ steps.app-token.outputs.token }} \
+            -o EducationalTools \
+            -p 4

ci/README.md

@@ -0,0 +1,152 @@
+# CI/CD Automation Scripts
+
+This directory contains automation scripts for managing GitHub issues and project boards.
+
+## Scripts Overview
+
+### 1. `issue.py` - Issue Management
+
+Automatically processes GitHub issues, particularly game requests:
+
+- Detects issues with `[Gmae Request]` prefix
+- Searches for relevant links on GitHub Pages
+- Posts automated comments with search results
+
+### 2. `move_to_production.py` - Project Board Automation
+
+Moves project items from "Done" status to "In Production" status:
+
+- Queries GitHub Projects v2 API using GraphQL
+- Finds all items with status "Done"
+- Updates them to "In Production" status
+- Used for production deployment automation
+
+### 3. `test_production_move.py` - Testing Script
+
+Manual testing script for the production move operation:
+
+- Allows testing the move operation without triggering workflows
+- Supports dry-run mode (future enhancement)
+- Useful for debugging and validation
+
+## GitHub Workflows
+
+### Issue Management (`.github/workflows/issue.yml`)
+
+Triggers on:
+
+- Issue opened
+- Issue edited
+
+Actions:
+
+- Runs `issue.py` script
+- Posts automated comments for game requests
+
+### Production Deployment (`.github/workflows/production_deploy.yml`)
+
+Triggers on:
+
+- Push to `prod` branch
+
+Actions:
+
+- Runs `move_to_production.py` script
+- Moves all "Done" items to "In Production" in project #4
+
+## Setup Requirements
+
+### GitHub App Configuration
+
+Both workflows use a GitHub App for authentication:
+
+1. **Secrets Required:**
+
+   - `GH_APP_ID` - Your GitHub App ID
+   - `GH_PRIVATE_KEY` - Your GitHub App private key
+
+2. **App Permissions:**
+   - Issues: Read & Write (for issue comments)
+   - Projects: Read & Write (for project board updates)
+   - Repository: Read (for workflow access)
+
+### Project Configuration
+
+The production deployment script assumes:
+
+- Organization: `EducationalTools`
+- Project number: `4`
+- Status field with options: "Done" and "In Production"
+
+These can be customized by modifying the workflow or script parameters.
+
+## Usage
+
+### Automatic Usage
+
+The workflows run automatically based on their triggers:
+
+- Issue workflow: When issues are opened/edited
+- Production workflow: When code is pushed to `prod` branch
+
+### Manual Testing
+
+To test the production move operation manually:
+
+```bash
+# Install dependencies
+pip install requests
+
+# Test with your GitHub token
+python ci/scripts/test_production_move.py --token YOUR_GITHUB_TOKEN
+
+# Test with different organization/project
+python ci/scripts/test_production_move.py \
+  --token YOUR_TOKEN \
+  --org YourOrganization \
+  --project 5
+```
+
+### Direct Script Usage
+
+You can also run the scripts directly:
+
+```bash
+# Process a specific issue
+python ci/scripts/issue.py -n 123 -t YOUR_TOKEN
+
+# Move project items to production
+python ci/scripts/move_to_production.py -t YOUR_TOKEN -o EducationalTools -p 4
+```
+
+## Dependencies
+
+- `requests` - HTTP client for GitHub API calls
+- `googlesearch-python` - For searching game links (issue.py only)
+
+## Error Handling
+
+The scripts include error handling for common scenarios:
+
+- Invalid tokens or permissions
+- Missing projects or fields
+- Network issues
+- GraphQL API errors
+
+## GraphQL Queries
+
+The project automation uses GitHub's GraphQL API v4 for efficient data retrieval and mutations. Key operations:
+
+1. **Project Data Query** - Gets project ID and field information
+2. **Items Query** - Retrieves all project items with their status values
+3. **Update Mutation** - Changes item status from "Done" to "In Production"
+
+## Future Enhancements
+
+Potential improvements:
+
+- Dry-run mode for testing changes
+- Support for custom field names
+- Better error reporting and logging
+- Slack/Discord notifications
+- Rollback capabilities