Action CI: cover multi-id only and skip on all three OSes

Open Beginner friendly
  • Is something wrong?
#71 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, markdown, python, yaml
Domain
build-system

Research direction

Start with the job in .github/workflows/ci.yml that runs uses: ./ and the only/skip input parsing in action.yml. Add matrix steps for only: project git on tests/fixtures/action-pass and only: project plus skip on tests/fixtures/action-fail, then update the "Not covered" note in ROADMAP.md. Done when the steps pass on Ubuntu, Windows and macOS and a deliberately broken space split makes a new step fail.

Written by the indexing model from the issue text.

Description

good first issue help wanted

Problem: The GitHub Action CI job (.github/workflows/ci.yml, job running uses: ./) only ever passes a single id to only (only: project) and never uses skip. Both inputs are documented as space-separated lists in action.yml, so a quoting or splitting bug on one OS would go unnoticed. ROADMAP.md lists this as not covered.

Do:

  • Add steps to the existing Ubuntu/Windows/macOS matrix job:
    • only: project git on tests/fixtures/action-pass: must succeed.
    • only: project plus skip: <the failing id> on tests/fixtures/action-fail: must succeed, proving skip removes the failure.
    • Optional: format: json + output, then assert with a short python -c that the skipped id is absent and both only prefixes are present.
  • Update the ROADMAP.md "Not covered" note (SARIF is already covered by the existing step, so the note is stale there too).

Done when:

  • The new steps pass on all three OSes.
  • Breaking the space splitting in action.yml makes at least one new step fail.

Notes:

  • No product code changes expected; CI and ROADMAP only.
  • Comment below to claim it and I will assign you.
Dominant language
Python
Stars
2
Forks
3
Avg merge
10h 51m
Merged PRs (30d)
40

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 Evalogical-Inc/devReady

All issues in Evalogical-Inc/devReady

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.