Auto deploy using semantic versioning
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Use commit messages to determine, update and publish the library versions on each merged pull request.
Note: The changelog file should also be updated.
Depends on https://github.com/imbrn/gs/issues/5
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 reviewing the dependency in issue #5 and the repository's current release and publishing setup. Determine how merged pull-request commit messages should drive semantic version updates and how the changelog file should be updated. Done means each merged pull request can trigger the version update, publication, and changelog update described here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100