Track CI failures

Open
#2,456 96 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Domain
ci-cd

Research direction

The issue names no files, tests, or specific CI job. Start by identifying the failing jobs and recording their error details; what counts as done cannot be defined until the failures and desired fixes are specified.

Written by the indexing model from the issue text.

Description

This issue exists in order to track errors in CI jobs.

Dominant language
Starlark
Stars
279
Forks
94
Avg merge
1d 12h
Merged PRs (30d)
10

Getting set up

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.

More from tweag/rules_haskell

All issues in tweag/rules_haskell

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.