armand1m / armand1m/create-formik-fields-comparator
build: Configure semantic-release correctly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
-
I'm submitting a ...
[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project -
Summary
As a developer,
I want to have semantic-release correctly setup,
So I can benefit from automatic version and changelog generation, commit tag and package deployment.
- Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)
Tried using npx semantic-release-cli setup but it didn't worked well on the CI. It seems some stuff as changed recently. Need to take a look on that.
Contributor guide
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
No files or tests are named in the issue. Start by inspecting the repository's CI configuration and current semantic-release setup; done means CI can generate versions and changelogs, create commit tags, and deploy the package automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100