oss-slu / oss-slu/DigitalBoneBox

Separate linting and test running tasks in Actions workflow

Open
#216 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #254 by @priya-dikey — closed without merging
enhancement good first issue
Dominant language
JavaScript
Stars
8
Forks
18
Avg merge
8h 17m
Merged PRs (30d)
4

Description

🎯 Goal / Objective

A clear and concise description of what this task aims to achieve. Why is this task important?

The Actions workflow at .github/workflows/lint.yml does both lint checking and test running. These are separate tasks that should be run individually in their own workflows. This way, if linting fails, it does not prevent the tests from being run or vice versa.


✅ Tasks to be Completed

A checklist of the specific, actionable steps required to complete this issue. This helps track progress.

  • Since the file is called lint.yml, remove the test running step from the file.
  • Add the test running step to a new file. Give it the same triggers as the lint job (push to main or PR to main).

Acceptance Criteria

A checklist of conditions that must be met for this task to be considered complete. How will we verify that it's done correctly?

  • Linting and testing are not done in the same job.
  • Both linting and testing run on the same triggers.

Additional Context

Add any other context, notes, screenshots, or links that might be helpful for completing this task.

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 inspecting .github/workflows/lint.yml and identify its current triggers and test-running step. Remove the test step from lint.yml, place it in a separate workflow with matching push-to-main and pull-request-to-main triggers, and verify the two tasks are no longer in the same job.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.