haskell-nix/hnix

Please, make a CI automation that tests the reverse dependencies

Open

#790 opened on Jan 2, 2021

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Nix (116 forks)github user discovery
automationgood first issue

Repository metrics

Stars
 (835 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

We currently, thankfully, have a pretty small amount of projects that actively use us: https://packdeps.haskellers.com/reverse/hnix

Take all reverse dependencies, and build them in CI. In that way during any API work we would see what downstream projects are using - that would distinguish what is really used from what project exposed vacuously.

That would help to clean-up the public API, which would save us a lot of effort in the future work.

Contributor guide

Research direction
Set up a CI job that fetches all reverse dependencies from the Hackage package database (e.g., via packdeps.haskellers.com) and builds them with the current hnix version, reporting any build failures. This will help identify downstream breakage during API changes.
Tech stack
haskell
Domain
ci cdbuild systemdevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
NixCIreverse dependencies
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60