☢️ Fallout — The C#/.NET Build System
C-Rank Grade: S (Elite) - 73/100
External PR Merge Rate: 81%
Response Time: 4h
First Timer Success: 100%
Fallout-build/Fallout has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Fallout-build/Fallout respond to incoming external pull requests in approximately 3.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 73.0 places Fallout-build/Fallout in the S tier.
The external contributor pull request merge rate for Fallout-build/Fallout is 80.8%, based on public PR activity from non-core contributors.
Fallout-build/Fallout currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/Fallout-build/Fallout?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~19 hours (36% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Problem FalloutBuild.NoLogo carries a pre-rebrand description in both the XML doc comment and the [Parameter] attribute (src/Fallout.Build/FalloutBuild.cs:138-141), so --help prints: --no-logo Disables displaying the NUKE logo. The same string is baked into the generated .fallout/build.schema.json, which drives IDE completion. Outcome User-facing parameter text names Fallout, not NUKE. Acceptance criteria --help shows "Disables displaying the Fallout logo." .fallout/build.schema.json regenerated A spec guards the built-in parameter descriptions against pre-rebrand product names Notes Scope is the user-facing parameter text only. Deliberate NUKE references (attribution, the ☢ survived the NUKE tagline, shim docs) stay.
Usage Information 10.3.49 Description Contrary to the information stated in the documentation for Parameters, the code is still looking for NUKE_. Problem Code: Fallout/src/Fallout.Build/Execution/ParameterService.cs Line 192 in f57634c GetTrimmedName(x.Key).EqualsOrdinalIgnoreCase($"NUKE{trimmedVariableName}")).ToList(); I can create a PR later to address this, but I am unsure if it should also remain compatible with NUKE_. LMK what you think. Reproduction Steps Create Build Project Add a string parameter. Assert in target when parameter is null. export FALLOUT_MY_PARAMETER_NAME="hello" Run build, reach assertion. export NUKE_MY_PARAMETER_NAME="hello" Run build, no assertion. Expected Behavior Environment variables prepended with FALLOUT_ should be used for parameters as per documentation. Actual Behavior See Repro. Regression? Kind of. Technically? Known Workarounds No
Why The only static analysis today is Qodana (code quality, not security). For enterprise positioning we need a SAST scanner that lands findings in the GitHub Security tab. CodeQL is the GitHub-native option, free for public repos, and supports C# (the bulk of this codebase). Scope Add .github/workflows/codeql.yml — checkout, init CodeQL, build, analyze. Languages: csharp (primary). Maybe add javascript later if the docs site moves into this repo. Schedule: on push to main + PRs targeting main, plus a weekly cron for advisory-database refresh. Ignore generated files: source/Nuke.Common/Tools/**/*.Generated.cs, build/_build/**/obj/**, build/Build.CI.*.cs (auto-generated). Done when CodeQL workflow committed First scan completes green (or findings triaged) GitHub Security tab populated
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to Fallout-build/Fallout, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of Fallout-build/Fallout acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 80.8% were successfully merged into the primary branch.
Fallout-build/Fallout has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 73.0 places Fallout-build/Fallout in the Elite tier.
The external pull request merge rate is 80.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Fallout-build/Fallout currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Fallout-build/Fallout are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.