nuke-build/nuke

🏗 The AKEless Build System for C#/.NET

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 12 minutes ago
Added to GitGenius on September 18th, 2026
Created on June 9th, 2017
Open Issues & Pull Requests: 121 (+0)
GitHub issues: Enabled
Number of forks: 457
Total Stargazers: 3,754 (+0)
Total Subscribers: 60 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.6 hours
Mean response time: 19.1 days
90th percentile: 28.4 days
Tracked items: 106

Most active contributors

Sign in to see contributor activity.

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 86% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 40
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 443 days
Stale 30+ days: 38
Stale 90+ days: 35

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (86)
  • enhancement (30)
  • area:core (1)
  • cost:high (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Nuke is a build automation system for C# and .NET projects that replaces traditional build scripts and YAML configuration files with regular C# console applications.

The tool addresses the friction developers experience when working with build automation by leveraging C# itself as the build language. Rather than context-switching to YAML or shell scripts, developers write build logic in C# with full access to object-oriented programming, IDE features like code completion and refactoring, and integrated debugging. The system handles common build automation concerns including parameter injection, cross-platform path abstraction, access to solution and project models, and reusable build step definitions that can be shared across repositories. Nuke can also generate CI/CD configuration files in YAML and other formats, with automatic parallelization of build steps across multiple agents to optimize pipeline throughput.

Teams should consider Nuke if they want to keep build logic within the C# ecosystem and avoid the cognitive load of switching between languages and tools. It suits projects where developers value consistency between application code and build code, and where teams want to apply standard refactoring and testing practices to their build definitions. The tool is particularly valuable for organizations managing multiple .NET repositories that need to share build logic patterns.

The project maintains active development with regular updates and demonstrates integration across multiple CI/CD platforms through self-hosted builds that serve as working examples. The codebase shows consistent attention to both core functionality and the developer experience of using the tool, with documentation and examples kept current alongside feature development.