tweag / tweag/rules_haskell

Use rules_img instead of rules_oci

Open
#2,425 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue P3 type: feature request
Dominant language
Starlark
Stars
279
Forks
93
Avg merge
13d 11h
Merged PRs (30d)
3

Description

Is your feature request related to a problem? Please describe.

https://github.com/bazel-contrib/rules_img is similar to rules_oci in spirit, but has much nicer optimizations.

Describe the solution you'd like
Add an example using rules_img equivalent to what is described in haskell-use-cases.rst and also update the documentation.

Describe alternatives you've considered

Additional context

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 by reading haskell-use-cases.rst and the existing rules_oci example it describes. Add an equivalent example using rules_img, then update the documentation; done means the example and related documentation consistently use the requested approach.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, documentation
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.