sbt/sbt-github-actions
58.8
Adequate · 7 November 2026
1.5k
lines of production code
Scala
primary language
4
measurements over time
What this system is
Features
Initial release of sbt-github-actions plugin
This change introduces the sbt-github-actions plugin, which allows sbt projects to automatically generate and maintain GitHub Actions workflow files (ci.yml and clean.yml) directly from the build definition. The plugin provides settings to configure build matrices (Scala/Java versions, OSes), JDK selection, caching, and publishing targets, while ensuring the generated workflows stay in sync with the build configuration. It also includes documentation for usage, Windows-specific setup, and integration with sbt-ci-release.
(repo-wide) · high confidence
Introduce generative GitHub Actions plugin with comprehensive configuration model
The \src/main\ area introduces the core of a new sbt plugin that generates GitHub Actions workflows (\ci.yml\ and \clean.yml\) from Scala configuration. \GenerativeKeys\ defines the settings API, allowing users to configure build matrices (Scala/Java/OS versions), publish triggers, timeouts, and environment variables. \GenerativePlugin\ implements the logic to render these settings into valid YAML, including support for job containers, services, and matrix inclusions/exclusions. The codebase also defines the underlying data models (\WorkflowJob\, \WorkflowStep\, \JavaSpec\, \RefPredicate\) and provides built-in actions for setting up Java (including GraalVM), sbt, and handling Windows pagefile fixes.
src/main · high confidence
Behavioural changes
Added symlink for main source directory
A new symbolic link named 'main' has been created in the project/src directory, pointing to the ../../src/main directory. This change establishes a local reference to the main source code location, likely to simplify path resolution or align with a specific project structure requirement.
project/src · low confidence
Test coverage
Added scripted tests for CI and clean workflow regeneration; Added scripted tests for GitHub workflow OSes clean publish; Added scripted tests for sbt native thin client; Added scripted tests for suppressed Scala version workflow generation; Added test for cross-Scala version stability; Added test for non-existent target handling; Initial unit tests for the workflow generation plugin; Test coverage for preserving action hashes during workflow updates.
Dependencies
Upgrade sbt build tool to version 1.12.2
The project's build definition has been updated to use sbt version 1.12.2, as specified in the newly created \project/project/build.properties\ file. This change also includes structural adjustments to the build project layout, such as adding symlinks for \libraries.sbt\ and \src/main\ to reference files in the parent directory, which supports the untying of the \sbt-github-actions\ cyclical dependency mentioned in the commit history.
project/project · high confidence
Upgrade to sbt 2.0.0 and Scala 2.12.20
The plugin's build has been upgraded to target sbt 2.0.0 for Scala 3 builds and sbt 1.5.5 for Scala 2.12, with the Scala compiler version bumped to 2.12.20. This change also updates the test dependency \specs2-core\ to version 4.20.8 and migrates the organization from \com.codecommit\ to \com.github.sbt\.
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 58 → 59 (+0.8)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 72 → 71 (-1.0)
- Architecture 100 → 100 (+0.0)
- Maturity 52 → 52 (+0.0)
- Readiness 52 → 55 (+3.2)
- Security 70 → 70 (+0.0)
Resolved (3)
- Method naming inconsistency: 'compileList' vs 'compileListOfSimpleDicts'. The first method name is generic and could imply any list, while the second is verbose and specific. If both are list-compilation helpers, they should follow a consistent naming pattern (e.g., compileList and compileMapList or compileDictList).
- Naming inconsistency between 'Build' and 'Publish' workflows. While these are distinct domains, the parallel structure suggests a unified naming convention for workflow generation keys. However, the more significant issue is the lack of a unified 'Workflow' key that encompasses both, or a consistent suffix pattern if they are meant to be separate. Given the extensive list of githubWorkflow* keys, this is a minor stylistic point rather than a functional redundancy.
- Off-boarding risk: anonymized user #1
New (2)
- GenerativePlugin.diff (cognitive 18) (src/main/scala/sbtghactions/GenerativePlugin.scala)
- Off-boarding risk: anonymized user #1
Changes since last survey
- 1 commits — 1 feature/other, 0 fixes
By area
- (repo) — 1 commit
Notable commits
- change: Merge pull request #236 from nafg/colored-workflow-diff
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
sbt/sbt-github-actions was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 7 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit c62aa656c835c2aae8a8c5adc86d965838c2a5fb — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-5f8314471808.