Publish GitHub release artifacts
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- Java
- Stars
- 197
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
It would be good to provide GitHub release artifacts from sbt-pack task running on travis.
There is some good example of this in ratatool: https://github.com/spotify/ratatool/blob/master/.travis.yml#L27
Contributor guide
No contributing guide indexed for this repository
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 inspecting the repository's Travis configuration and the sbt-pack task, then compare the referenced ratatool .travis.yml example around line 27. Verify how GitHub release artifacts are expected to be created and published; done means a Travis build produces downloadable artifacts for a GitHub release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, java, scala
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100