typelevel / typelevel/sbt-typelevel
Reconcile with upstream sbt-github-actions
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 185
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/sbt/sbt-github-actions
sbt-typelevel made its own fork of sbt-github-actions when it was in a lull, and I was moving fast. Since then @mdedetrich has revived maintenance on the upstream plugin, which is now published under sbt org. The original intent was always to reconcile with upstream, and now the time has come.
For this to be successful, we will need to:
- upstream our changes in the fork (several have already been upstreamed)
- re-integrate sbt-typelevel with the upstream plugin
- have a dedicated maintainer on the upstream plugin, to review PRs in context of how we use the plugin in sbt-typelevel
The benefits will be shared maintenance with the wider community and access to several interesting features happening upstream (e.g., customizable workflow permissions, multiple workflow files, etc.).
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 comparing the sbt-typelevel fork with https://github.com/sbt/sbt-github-actions, then review how the current plugin is integrated in this repository. Done means the fork's remaining changes are upstreamed, sbt-typelevel uses the upstream plugin, and a dedicated upstream maintainer is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, scala
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100