Callers#
Projects whose repositories call a StroggForge workflow, as recorded in war-room/ecosystem.toml. Rust manufacturing goes through rustGlobalBuild and libGlobalBuild; Mod Template sites go through modGlobalBuild, which Rust repositories reach through mod_template.
- libGlobalBuild: dream_path / dream-path, dream_archive, vfstool_lib, openmw-config, L3i / l3i, dream-net, dream-soft-render
- modGlobalBuild: DreamWeave-Mod-Template, S3ctors-S3cret-St4sh / St4sh
- rustGlobalBuild: VFSTool, S3LightFixes, Morrobroom, greenmote, dream-ini, dream_archivetool
Binary integration template#
Review permissions, secrets, publish flags, binary/package selection and the pinned ref. Source: .github/action_templates/rust_template.yaml.
name: Application CI
on:
workflow_dispatch:
pull_request:
push:
# Keep branch pushes restricted to main. Non-tag pushes publish to the shared
# "development" release, so feature branches will compete for the same release.
branches: main
tags: ['*']
jobs:
build:
permissions:
contents: write
pages: write
id-token: write
uses: DreamWeave-MP/StroggForge/.github/workflows/rustGlobalBuild.yml@v72
secrets: inherit
with:
# Required: JSON array of binary names to build. Add more for monorepos.
binary_names: '["ENTER_BINARY_NAME_HERE"]'
# Optional: the Cargo package that provides the binaries, when they live in a workspace
# member rather than the root package or a directory named after the binary.
# Use `workspace` to build each binary from whichever member defines it.
# binary_package: ENTER_PACKAGE_NAME_HERE
# Optional: extra files or directories for every release archive.
# include_files: "README.md,LICENSE"
# Optional: uncomment if the package is published to the AUR.
# aur_package_name: ENTER_PACKAGE_NAME_HERE
# git_username: ENTER_USERNAME_HERE
# git_email: ENTER_EMAIL_HERE
# Optional: set NEXUS_API_KEY and NEXUS_GROUP_IDS repository or organization secrets
# to upload release archives to Nexus Mods. Use StroggForge's
# .github/nexus_group_ids.template.json as the NEXUS_GROUP_IDS shape.
# Optional: uncomment to notify dependent repositories on tagged releases.
# dependent_repo_names: |
# DreamWeave-MP/DW-tools
# Optional: set false if this project uses its own SSG for docs.
# publish_docs: false
# Optional: set true if this repository is a DreamWeave Mod Template site. Once the release
# is published, the Mod Template stage records its archives in mod.lock and builds and deploys
# the site in place of rustdoc. With cargo_publish_workspace, a library the site also lists
# is recorded from crates.io in the same run. Grant `actions: write` in the permissions above
# as well.
# mod_template: true
# Optional: set false if this project does not publish to crates.io.
# cargo_publish: false
# Optional: publish every workspace member in dependency order instead of one crate per binary.
# cargo_publish_workspace: true
# Optional: check the workspace on its minimum supported Rust version before release.
# Use a version such as '1.88', or `auto` to read rust-version from Cargo.toml.
# msrv: auto
# Optional: set true if this project has Criterion benchmarks.
# generate_benchmarks: true
# Optional: set true to build Android ARM64 ELF release artifacts targeting API level 23.
# This does not produce an APK.
# enable_android: true
# Optional: set true to build Portmaster ARM64 release artifacts.
# Uses aarch64-unknown-linux-gnu with an EL9 sysroot for glibc 2.34 compatibility.
# enable_portmaster: true
# Optional: a directory of muOS app files, such as mux_launch.sh. Each PortMaster archive is
# packaged with them as <binary>-Portmaster-ARM64.muxapp and published beside it.
# Requires enable_portmaster.
# muxapp_dir: "My App"
# Optional: copy StroggForge's scripts/cargo-build-args.example.sh to
# .stroggforge/cargo-build-args.sh and run chmod +x on it if release builds
# need platform-specific Cargo features. Corprus Crucible runs it automatically
# when present and only accepts Cargo feature arguments from stdout.
# Optional: set false if the project is not hosted by DreamWeave or does not use discord notifications
# generate_discord_notification: falseLibrary integration template#
crate_names must match Cargo [package].name. Enable cargo_publish_workspace for dependency-ordered workspace publishing. Source: .github/action_templates/lib_template.yaml.
name: Library CI
on:
workflow_dispatch:
pull_request:
push:
# Keep branch pushes restricted to main. Non-tag pushes publish to the shared
# "development" release, so feature branches will compete for the same release.
branches: main
tags: ['*']
jobs:
build:
permissions:
contents: write
pages: write
id-token: write
uses: DreamWeave-MP/StroggForge/.github/workflows/libGlobalBuild.yml@v72
secrets: inherit
with:
# Required: JSON array of crate names. Must match [package].name in Cargo.toml.
# Add more entries for workspaces with multiple publishable crates.
crate_names: '["ENTER_CRATE_NAME_HERE"]'
# Optional: uncomment to notify dependent repositories on tagged releases.
# dependent_repo_names: |
# DreamWeave-MP/DW-tools
# Optional: set false if this project uses its own SSG for docs.
# publish_docs: false
# Optional: set true if this repository is a DreamWeave Mod Template site. The Mod Template
# stage records each version crates.io has in mod.lock and builds and deploys the site in
# place of rustdoc. Grant `actions: write` in the permissions above as well.
# mod_template: true
# Optional: set false if this project does not publish to crates.io.
# cargo_publish: false
# Optional: publish every workspace member in dependency order instead of one crate per crate name.
# cargo_publish_workspace: true
# Optional: check the workspace on its minimum supported Rust version before release.
# Use a version such as '1.88', or `auto` to read rust-version from Cargo.toml.
# msrv: auto
# Optional: set true if this project has Criterion benchmarks.
# generate_benchmarks: true
# Optional: set false if another workflow in the same run already sends the discord notification.
# generate_discord_notification: falseMod Template integration template#
For a site of mods, as build_site.yml. Rust repositories set mod_template: true on their application or library caller instead. Source: .github/action_templates/mod_template.yaml.
name: Build, release and publish
# A DreamWeave Mod Template site of mods, as build_site.yml. Rust repositories do not use this
# file: their rustGlobalBuild or libGlobalBuild caller sets mod_template: true instead.
on:
push:
branches: ['**']
# Release tags only: a version always starts with a digit, and slugs cannot contain '-'.
tags: ['*-[0-9]*']
pull_request:
workflow_dispatch:
permissions:
contents: read
concurrency:
group: dreamweave-${{ github.ref }}
cancel-in-progress: ${{ !(github.event_name != 'pull_request' && (github.ref_type == 'tag' || github.ref_name == github.event.repository.default_branch)) }}
jobs:
site:
permissions:
actions: write # the default-branch run a release tag starts
contents: write # releases, and the mod.lock commit
id-token: write # Sigstore and Pages
pages: write
uses: DreamWeave-MP/StroggForge/.github/workflows/modGlobalBuild.yml@v72
secrets: inheritDaily quality template#
Scheduled fmt/Clippy/RustSec checks with no release secrets. It calls setup-llvm directly because Clippy compiles. Source: .github/action_templates/daily_quality_template.yaml.
name: Daily Rust Quality Checks
on:
workflow_dispatch:
schedule:
# GitHub cron is UTC. 15:00 UTC is 9 AM Central Standard Time.
- cron: '0 15 * * *'
permissions:
contents: read
jobs:
fmt:
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v6
with:
submodules: true
- uses: dtolnay/rust-toolchain@stable
- name: Run rustfmt
run: cargo fmt --all --check
clippy:
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v6
with:
submodules: true
- uses: dtolnay/rust-toolchain@stable
# Every DreamWeave crate builds with clang and lld matching rustc's LLVM.
- uses: DreamWeave-MP/StroggForge/.github/actions/setup-llvm@v72
- name: Run Clippy
run: cargo clippy --workspace --all-targets --all-features -- -W clippy::pedantic -D warnings
audit:
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v6
with:
submodules: true
- uses: dtolnay/rust-toolchain@stable
- uses: taiki-e/install-action@cargo-audit
- name: Run Cargo audit
run: cargo auditBenchmark template#
Runs cargo bench by hand from the Actions tab, on the runner and with the filter it is given, and keeps BENCHMARKS.md in the run's summary and artifacts. No pull request waits for it. Source: .github/action_templates/benchmark_template.yaml.
name: Benchmarks
# Run by hand from the Actions tab: benchmarks are never part of pull request validation.
on:
workflow_dispatch:
inputs:
os:
type: choice
description: "The runner to measure on"
default: ubuntu-24.04
options:
- ubuntu-24.04
- macos-latest
- macos-26-intel
- windows-2025-vs2026
filter:
type: string
description: "Run only the benchmarks whose ID contains this (cargo bench -- <filter>)"
required: false
default: ''
all_features:
type: boolean
description: "Benchmark with every feature enabled"
default: false
permissions:
contents: read
jobs:
benchmarks:
uses: DreamWeave-MP/StroggForge/.github/workflows/benchmarks.yml@v72
with:
os: ${{ inputs.os }}
filter: ${{ inputs.filter }}
all_features: ${{ inputs.all_features }}