privatecoffee-website/.forgejo/workflows/build-dev.yml
Kumi 1c9e1d6c68
fix(ci): force push to 'pages-dev' branch in build-dev workflow
Changed the force push target from 'pages' to 'pages-dev' to ensure the dev build process does not interfere with the production pages. This helps maintain a clear separation between development and production environments, reducing the risk of unintentional overwrites.
2024-07-01 10:34:16 +02:00

49 lines
1.3 KiB
YAML

name: Build and Deploy Static Site
on:
push:
branches:
- dev
jobs:
build:
container: node:20-bookworm
steps:
- name: Checkout repository
uses: actions/checkout@v3
- name: Install dependencies
run: |
apt update
apt install -y python3 python3-pip
python3 -m pip install -r requirements.txt --break-system-packages
- name: Generate static site
run: python3 main.py
- name: Deploy to pages branch
run: |
# Configure Git
git config --global user.name "Forgejo"
git config --global user.email "noreply@private.coffee"
# Move generated static site files to a temporary location
mv build ../static_site_temp
# Create a new orphan branch named 'pages-dev'
git checkout --orphan pages-dev
# Remove all files from the working directory
git rm -rf .
# Move the static site files back to the working directory
mv ../static_site_temp/* ./
mv ../static_site_temp/.* ./ 2>/dev/null || true
# Add and commit the static site files
git add .
git commit -m "Deploy static site"
# Force push to the 'pages-dev' branch
git push origin pages-dev --force