Info annotations mark the workflow as failed

Open
#90 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
ci-cd, tooling

Research direction

Start by reproducing the package-check workflow behavior and tracing how informational annotations affect its final status. No file, test, or entry point is named, so first locate the workflow-status handling and determine which existing test or workflow run demonstrates the failure; done means info annotations no longer mark the workflow as failed.

Written by the indexing model from the issue text.

Description

This issue has no description.

Dominant language
Rust
Stars
37
Forks
9
Avg merge
7d 3h
Merged PRs (30d)
6

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 typst/package-check

All issues in typst/package-check

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.