semantic-release / semantic-release/exec
Extract `npx lockfile-lint --path package-lock.json` from test workflow
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 164
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, testing
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100