domains / families / software-engineering / scenario-godot-pipeline-automation

scenario-godot-pipeline-automation

separate

Use when Godot 4.7 work must run without a mouse or at scale: batch import of hundreds of GLB props or an AI image-to-3D art drop, naming rules, import presets and post-import scripts, editor plugins, EditorScript and @tool, EditorImportPlugin, GUT or gdUnit4 tests in CI, a GitHub Actions export workflow, GDExtension basics, or a Godot MCP server; also when --import is slow, textures stay uncompressed, tests pass locally but CI fails, or an export ships test folders.

When to use

• batch import of hundreds of GLB props
• AI image-to-3D art drop processing
• naming rules and import presets
• post-import scripts and editor plugins
• EditorScript and @tool usage
• EditorImportPlugin implementation
• GUT or gdUnit4 tests in CI
• GitHub Actions export workflow

When not to use

• starting Godot directly
• godot-cpp builds
• Rust builds
• scons or cargo execution

Skill page

Source