Redoing this properly against the Add template.
1. Has your repository on GitHub existed at least 3 months?
The Fallout-build/Fallout repo node is ~6 weeks old (created 2026-05-18), but it's a hard fork of nuke-build/nuke — a 5+ year-old mature project already on this list. Full commit history carried over; only the rename to Fallout is recent. It's under credible new maintenance: co-maintained by Dennis Doomen (creator of FluentAssertions), a long-standing, well-known name in the .NET OSS community.
2. Why is it awesome?
Fallout is the maintained continuation of NUKE. NUKE's original author stopped maintaining it and preferred it not be continued under the NUKE name, so it was hard-forked and renamed. Fallout keeps NUKE's model — the build is itself a cross-platform, type-safe C# console app — and is under active new maintenance in 2026 (calendar-versioned releases, ongoing rebrand + plugin work). Since NUKE is now unmaintained, this keeps Build Automation pointing at the living project.
3. Does your PR follow alphabet-ordering?
Yes — removes the Nuke line and inserts Fallout alphabetically (before FlubuCore).
3. Is it .NET Core / .NET Standard?
Yes — modern cross-platform .NET (targets .NET 10); Windows/Linux/macOS.
4. Checked README/issues for duplicates?
Yes. This replaces the existing Nuke entry rather than duplicating, since it's the same project under a new name.
PR to follow.
Redoing this properly against the Add template.
1. Has your repository on GitHub existed at least 3 months?
The
Fallout-build/Falloutrepo node is ~6 weeks old (created 2026-05-18), but it's a hard fork of nuke-build/nuke — a 5+ year-old mature project already on this list. Full commit history carried over; only the rename to Fallout is recent. It's under credible new maintenance: co-maintained by Dennis Doomen (creator of FluentAssertions), a long-standing, well-known name in the .NET OSS community.2. Why is it awesome?
Fallout is the maintained continuation of NUKE. NUKE's original author stopped maintaining it and preferred it not be continued under the NUKE name, so it was hard-forked and renamed. Fallout keeps NUKE's model — the build is itself a cross-platform, type-safe C# console app — and is under active new maintenance in 2026 (calendar-versioned releases, ongoing rebrand + plugin work). Since NUKE is now unmaintained, this keeps Build Automation pointing at the living project.
3. Does your PR follow alphabet-ordering?
Yes — removes the
Nukeline and insertsFalloutalphabetically (beforeFlubuCore).3. Is it .NET Core / .NET Standard?
Yes — modern cross-platform .NET (targets .NET 10); Windows/Linux/macOS.
4. Checked README/issues for duplicates?
Yes. This replaces the existing
Nukeentry rather than duplicating, since it's the same project under a new name.PR to follow.