Fallout.Utilities.IO.Globbing 10.4.0

<p align="center"> <img width="320" src=".assets/fallout-logo.svg" alt="Fallout — .NET build system" /> </p>

<p align="center"> <strong>📖 Documentation: <a href="https://docs.fallout.build/">docs.fallout.build</a></strong> </p>

📦 Fallout is the successor to NUKE. Migrating from NUKE →

Fallout

Build automation for C#/.NET — the hard-fork successor to NUKE.

Based on NUKE

Fallout is the successor to NUKE, originally created by Matthias Koch (matkoch) and many contributors. Fallout continues NUKE's mission as a C#-first build automation framework for .NET — under new maintenance, with an enterprise-CI/CD focus.

The original NUKE code is preserved here under the MIT License with attribution. Major version 10.x was the last NUKE release; everything from this fork forward carries the Fallout identity.

Migrating from NUKE

If you maintain a NUKE-based build, docs/migration/from-nuke.md walks you through it. The short version:

dotnet tool install -g Fallout.Migrate
cd path/to/your-nuke-repo
fallout-migrate

Install

dotnet tool install -g Fallout.GlobalTool

The CLI installs as fallout. Verify with fallout --help.

dotnet tool uninstall -g Fallout.GlobalTools

For per-repo manifest pinning (.config/dotnet-tools.json), project setup, and shell completion, see the Installation guide on docs.fallout.build.

Table of Contents

• Elevator Pitch
• Build Status
• Activity
• Sponsorship

Elevator Pitch

Solid and scalable CI/CD pipelines are an essential pillar for being competitive and creating a great product. But why are most of us a little afraid of touching YAML files and don't even dare to look at build scripts? Much of this is because C# developers are spoiled with a great language and smart IDEs, and they don't like missing their buddy for code-completion, ease of debugging, refactorings, and code formatting.

Fallout (NUKE's successor) brings your build automation to an even level with every other .NET project. How? It's a regular console application allowing all the OOP goodness! Besides, it solves many common problems in build automation, like parameter injection, path separator abstraction, access to solution and project models, and build step sharing across repositories. Fallout can also generate CI/CD configurations (YAML, etc.) that automatically parallelize build steps on multiple agents to optimize throughput!

Build Status

CI runs on every PR targeting main, release/*, or support/* on build.yml (Linux) — its ubuntu-latest job is the only required status check. Cross-platform Test+Pack (Windows + macOS) is gated to release intent — PRs into release/* / support/* and v* tag pushes — via build-cross-platform.yml; it does not run on routine main work. A …-preview prerelease is published to GitHub Packages under the reserved Fallout.* prefix on every push to main. Stable releases fire from release/YYYY tags via .github/workflows/publish-packages-release.yml (GitHub Packages + GitHub Releases by default; nuget.org opt-in per release). Docs-only PRs are served by a no-op companion workflow (build-skip) so branch protection is satisfied without spending CI minutes on a real build.

Workflow	Status	Trigger
build		PR to main / release/* / support/* (code paths) — job ubuntu-latest is the required check
build-cross-platform		PR to release/* / support/* or v* tag push — Windows + macOS (release intent)
publish-packages-preview		push to main → …-preview prerelease to GitHub Packages
publish-packages-release		tag push on release/YYYY (stable) or support/* (legacy/retired) — nuget.org opt-in

Multi-provider CI support (Azure Pipelines, GitLab, TeamCity, AppVeyor) was removed during the takeover and is being revived demand-driven — see #8.

Activity

Commits, issues, PRs (rolling 30 days)

Generated by Repobeats.

Stars over time

Generated by repostars.dev. Auto-updates as new stargazers arrive.

Sponsorship

Fallout is volunteer-run. There's no donation channel yet, but we want to be transparent about what running the project costs — see costs.md for the full list. If you or your organisation would like to help offset those costs, open an issue and we'll work out the details.

Credits

• Matthias Koch and the NUKE contributors — for creating and maintaining NUKE through version 10.x.

If you maintained or contributed to NUKE and want to be credited differently here, please open an issue.