export-pipeline

Automate Godot project exports across Windows, Linux, Web, Android, and iOS with CI/CD.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/GOODDAYDAY/Harness-Everything-Game-Framework --skill export-pipeline-gooddayday
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: export-pipeline
Source: https://github.com/GOODDAYDAY/Harness-Everything-Game-Framework/tree/main/.harness/skills/export-pipeline
Command: npx skills add https://github.com/GOODDAYDAY/Harness-Everything-Game-Framework --skill export-pipeline-gooddayday

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exporting and distributing Godot projects across multiple platforms is tedious and error-prone, requiring consistent presets, compatibility checks, and CI/CD configuration.

Core Features & Use Cases

  • Centralized management of export_presets.cfg and platform settings for multiple targets
  • CI/CD integration with GitHub Actions to automate builds, releases, and distribution
  • Guidance on signing, packaging, and deployment for cross-platform Godot games

Quick Start

Run the export pipeline to generate platform builds and publish artifacts via GitHub Actions.

Frequently Asked Questions about export-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Godot game exports for multiple platforms using CI/CD?

Automating Godot exports involves configuring a CI/CD pipeline with GitHub Actions, applying centralized export_presets.cfg management to build and distribute games across Windows, Linux, Web, Android, and iOS.

What do I need to set up a Godot export pipeline for Android and iOS?

Setting up a Godot export pipeline requires a committed export_presets.cfg file and environment-variable secrets configured in your CI/CD for signing and deploying Android and iOS builds.

Why are my Godot cross-platform builds failing in GitHub Actions?

Godot cross-platform builds often fail in GitHub Actions due to inconsistent export presets or missing environment-variable secrets required for platform-specific signing and deployment configurations.

What is the best way to manage export presets for multi-platform Godot releases?

The best way to manage export presets for multi-platform Godot releases is through centralized export_presets.cfg control integrated directly into a CI/CD automation workflow.

Does this Godot export automation work without committed export_presets.cfg?

No, this Godot export automation requires a committed export_presets.cfg file to properly apply platform settings and manage cross-platform builds within the CI/CD integration.