citrusframework / citrusframework/citrus
changelog - write or generate?
- Dominant language
- Java
- Stars
- 485
- Forks
- 155
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 6
Description
conventional commits are the de facto standard for keeping git history clean, automatic versioning and release notes and/or changelog generation. that is one possibility, tho Maven integration is almost non-existent. there are ways to combine Maven and Node.js.
another possibility is of course, to write a changelog manually.
what do you think @christophd? i personally tend to say, that an automatic integration may be overkill.
Contributor guide
Research direction
Start by reviewing the issue discussion and the repository's existing release and changelog process; no specific file, test, or entry point is named. The work is done when the project has a decided approach for manual changelogs or Maven/Node.js-based generation, with the required scope documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, node.js
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100