feat(pipeline): Migration from Gitea pipeline to act runner

README.md

@@ -4,11 +4,48 @@ A comprehensive platform for digital applications, approvals, and discussions, d
 
 ## Documentation
 
-For detailed documentation, architecture, and development guidelines, see [claude.md](./claude.md).
+For detailed documentation, architecture, and development guidelines, see [CLAUDE.md](./CLAUDE.md).
 
-## Issues
+## CI/CD with Act
 
-### Pipeline Issues
+This project uses [nektos/act](https://nektosact.com/) for local workflow execution. Workflows are defined in `.github/workflows/` in GitHub Actions format.
 
-- Gitea config can cause issues. When runner is not picking up jobs, run runner without config.
-- Backend tests fail when a Postgres database is running on the host machine.
+### Running Workflows Locally
+
+```bash
+# List available workflows and jobs
+act -l
+
+# Run specific jobs
+act -j frontend    # Run frontend job only
+act -j backend     # Run backend job only
+
+# Run all jobs for push event
+act push
+
+# Run with secrets (required for Docker push and deployment)
+act push --secret-file .secrets
+
+# Dry run to see what would execute
+act -n
+
+# Run a specific workflow file
+act -W .github/workflows/pipeline.yaml
+```
+
+### Setup
+
+1. Ensure [act](https://nektosact.com/) is installed (already available locally)
+2. Copy `.secrets.example` to `.secrets` and fill in your credentials:
+   ```bash
+   cp .secrets.example .secrets
+   # Edit .secrets with your actual tokens/keys
+   ```
+3. The `.actrc` file contains default configuration for act
+
+### Important Notes
+
+- **Manual Execution**: Workflows must be run manually via `act` command
+- **Secrets Required**: Docker push and deployment require secrets from `.secrets` file
+- **No Automation**: Unlike traditional CI/CD, act runs locally on demand
+- Backend tests may fail if PostgreSQL is running on the host machine