typelevel / typelevel/sbt-typelevel

Investigate / refresh the `clean` workflow.

Open
#856 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue
Dominant language
Scala
Stars
185
Forks
62
PR merge metrics
No merged PRs in 30d

Description

https://github.com/typelevel/sbt-typelevel/blob/ceb8c3e515400f4e78c9d9314824d3eb1a43919e/.github/workflows/clean.yml#L8

This was inherited from sbt-spiewak and hasn't been touched since, as far as I can remember. Occasionally it causes issues, when artifacts get clobbered before they can be published.

We should investigate (1) if such a workflow is still needed, in modern GHA and (2) if it is, if we can implement it more robustly.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with .github/workflows/clean.yml at the linked line and inspect how the clean workflow interacts with artifact publication. Determine whether modern GitHub Actions still requires this workflow, then assess a more robust approach that prevents artifacts from being clobbered before publication. Done means the workflow is either justified and reliable or removed with its necessity documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
build-system, ci-cd
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.