Extract `npx lockfile-lint --path package-lock.json` from test workflow

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
ci-cd, testing

Research direction

Start by locating the test workflow and the scripts in package.json that are invoked by npm t, then compare how the lockfile-lint command is currently run. Move the command into the appropriate package.json script and remove it from the workflow; done means npm t still runs the check successfully.

Written by the indexing model from the issue text.

Description

          for the other repos with more recent changes, we've moved this into the scripts in `package.json` that end up getting called from `npm t`

this changeset is a good reference for the group of changes that are related to what i'm highlighting here. i would also be ok with these changes being a follow-up to this PR, but the changes you are making in this PR set us up for those changes to make sense whichever way you decide is best

Originally posted by @travi in https://github.com/semantic-release/exec/pull/411#discussion_r1807034561

Dominant language
JavaScript
Stars
164
Forks
28
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 semantic-release/exec

All issues in semantic-release/exec

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.