typelevel / typelevel/sbt-typelevel
Project verification job
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 185
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
Half-baked idea:
*githubWorkflowCheck runs everywhere, but doesn't vary by JVM or Scala version
- This is also true of
scalafmtSbtCheck. - It would also be true of prospective validation of scala-steward.conf
Should there be a project job for the project-level verifications, so they're run only once? They aren't that slow, so it's not a priority, but getting these wrong fails lots of jobs right now.
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 by tracing how githubWorkflowCheck and scalafmtSbtCheck are configured across the JVM and Scala version matrix. Determine how a project-level verification job could run these checks once, including prospective scala-steward.conf validation, and define completion as project-level checks no longer being repeated in every matrix job.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100