Some checks failed
Release - Northern Thailand Ping River Monitor / Create Release (push) Failing after 1s
Release - Northern Thailand Ping River Monitor / Build Release Images (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Test Release Build (3.10) (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Test Release Build (3.11) (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Test Release Build (3.12) (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Test Release Build (3.9) (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Security Scan (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Deploy Release (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Validate Release (push) Has been skipped
Security & Dependency Updates / Dependency Security Scan (push) Failing after 1s
Security & Dependency Updates / Docker Security Scan (push) Failing after 1s
Security & Dependency Updates / License Compliance (push) Failing after 1s
Security & Dependency Updates / Check for Dependency Updates (push) Failing after 1s
Security & Dependency Updates / Code Quality Metrics (push) Failing after 1s
Release - Northern Thailand Ping River Monitor / Notify Release (push) Successful in 1s
Security & Dependency Updates / Security Summary (push) Failing after 3s
Checkout Action Migration: - Replace all 'actions/checkout@v4' with 'https://gitea.com/actions/checkout' - Fixes 'Bad credentials' errors when workflows try to access GitHub API - Native Gitea checkout action eliminates authentication issues - Applied across all 4 workflow files (CI, Security, Release, Docs) Version Increment: 3.1.1 3.1.2 - Core application version updates - Web API version synchronization - Documentation version alignment - Badge and release example updates Problem Solved: - Workflows no longer attempt GitHub API calls - Gitea-native checkout action handles repository access properly - Eliminates 'Retrieving the default branch name' failures - Cleaner workflow execution without authentication errors Files Updated: - 4 workflow files: checkout action replacement - 13 files: version number updates - Consistent v3.1.2 across all components Benefits: - Workflows will now run successfully in Gitea - No more GitHub API authentication failures - Native Gitea action compatibility - Ready for successful CI/CD pipeline execution
35 lines
1.1 KiB
Batchfile
35 lines
1.1 KiB
Batchfile
@echo off
|
|
REM Git initialization script for Northern Thailand Ping River Monitor
|
|
|
|
echo 🏔️ Initializing Git repository for Northern Thailand Ping River Monitor
|
|
|
|
REM Initialize git repository
|
|
git init
|
|
|
|
REM Add remote origin
|
|
git remote add origin https://git.b4l.co.th/B4L/Northern-Thailand-Ping-River-Monitor.git
|
|
|
|
REM Add all files
|
|
git add .
|
|
|
|
REM Initial commit
|
|
git commit -m "Initial commit: Northern Thailand Ping River Monitor v3.1.2
|
|
|
|
Features:
|
|
- Real-time water level monitoring for Ping River Basin
|
|
- 16 monitoring stations from Chiang Dao to Nakhon Sawan
|
|
- FastAPI web interface with station management
|
|
- Multi-database support (SQLite, MySQL, PostgreSQL, InfluxDB, VictoriaMetrics)
|
|
- Comprehensive monitoring and health checks
|
|
- Docker deployment with Grafana integration
|
|
- Production-ready architecture with CI/CD pipeline"
|
|
|
|
echo ✅ Git repository initialized successfully!
|
|
echo.
|
|
echo Next steps:
|
|
echo 1. Review and edit .env file with your configuration
|
|
echo 2. Push to remote repository:
|
|
echo git push -u origin main
|
|
echo.
|
|
echo 3. Start the application:
|
|
echo python run.py --web-api |