Resets the remote URL using authentication tokens before pushing.
This ensures the correct credentials are used for force pushes to the deployment branches.
Updates cron expressions in build workflows to trigger
job execution at 00:00 daily instead of hourly. This
reduces unnecessary build frequency and optimizes
system resource usage.
Replaces the Python-based container with
the new static-site-builder image across
multiple build workflows. This change
simplifies setup by removing explicit
NodeJS installation steps, likely aiming
to optimize the build process using a
more tailored environment.
Switches build container to Python 3.13 to align with
project dependencies and ensures node installation for
static site generation. Adjusts branch trigger to 'dev'
for testing in non-production environments.
Moves nodejs and npm installation to a dedicated step
to improve organization and clarity of the workflow file.
This separation optimizes the build process by detailing
package dependencies more clearly.
Adds cron schedules to trigger build workflows hourly for
development and main branches for better automation.
Updates blog generation to skip future-dated posts unless in
development mode, enhancing content management.
Included a --theme pride parameter to the generate static site
command in the build workflow. This allows theme customization
during site generation, enhancing site appearance and flexibility.
Set up a new GitHub Actions workflow to automate the build and deployment of the static site with the Pride theme on pushes to the main branch. This includes checking out the repository, installing dependencies, generating the site, and deploying to a new 'pages-pride' branch.
Ensures streamlined and consistent deployment aligned with updates.
Updated the build-dev CI workflow to run the static site generation with a development flag. This ensures the build script runs in the appropriate context for development environments. No issues referenced.
Added copying of .gitignore to the temporary static site location in both development and production build scripts. This prevents unnecessary files from being included in the new orphan branches, ensuring a cleaner and more efficient build process.
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.
Renamed 'build.yml' to 'build-dev.yml' to clarify its purpose for development builds. Updated branch triggers and orphan branch naming to 'dev' and 'pages-dev' respectively to distinguish development deployment processes from production. This enhances workflow clarity and separation of concerns in CI/CD practices.
- Added a new GitHub Actions workflow for the development branch to build and deploy the static site.
- Modified the existing workflow to trigger on the main branch instead of the static branch.
- Refactored the main.py script for consistency in string quotation.
The new workflow simplifies deployment processes during development, ensuring seamless and automated integration and testing.
Condensed the installation commands to streamline the setup process. Removed redundant pip upgrade step to avoid potential conflicts and expedite build workflow. No change to the overall functionality or dependency management.
Updated the build script to use `python3` and `pip3` commands, ensuring compatibility with environments where Python 2 might be the default. Also added `--break-system-packages` flag to `pip3` install to handle specific package installations without breaking the environment.
Replaces `runs-on` with `container` to utilize a Docker container
for node:20-bookworm. This enhances consistency and reproducibility
by standardizing the build environment across different runs.
Set up a GitHub Actions workflow to build and deploy the static site from the 'static' branch to the 'pages' branch. This workflow includes steps to install dependencies, generate the static site using Python, and handle deployment through Git configuration and git commands.
