Use Scala major versions rather than patch for generated actions
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 199
- Forks
- 67
- Avg merge
- 6h 24m
- Merged PRs (30d)
- 3
Description
When generating the various github action workflows sbt-github-actions uses the full Scala version (i.e. https://github.com/sbt/sbt-github-actions/blob/main/.github/workflows/ci.yml#L26). sbt now supports running a build against a specific Scala major version instead of the full patch version with the .x syntax, i.e. sbt ++2.12.x will load the sbt build with the the Scala 2.12 version defined by scalaVersion sbt setting.
Ultimately this solution would make the generated github action workflows less brittle when Scala patch versions are updated (i.e. no change is necessary). In turn this also makes it easier to add github status checks for workflows that Involve a Scala version since its only sensitive to epic/major instead of the whole version.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the generated workflow example in .github/workflows/ci.yml at line 26 and compare how Scala versions are currently represented. Update the generated GitHub Actions workflows to use the Scala major-version .x syntax so patch-version updates do not require workflow changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, scala
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100