[SCM-924] Enhance SCM changelog model to hold information about tagged commits
- Dominant language
- Java
- Stars
- 104
- Forks
- 189
- Avg merge
- 17h 46m
- Merged PRs (30d)
- 6
Description
**[Sven Linstaedt](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tzwoenn)** opened **[SCM-924](https://issues.apache.org/jira/browse/SCM-924?redirect=false)** and commented
Hi, in order to support something like semantic releases via maven directly and not some 3rd party tools, not only being able to create tags, but also processing them as part of the changelog would be great.
Tag information are are part of the commit history, accessible via git commandline
`git log --decorate`
This additional information could be parsed to enhance the ChangeSet model containing optional information about any tags for this particular commit.
A patch at least for gitexe could be provided, if needed.
---
**Affects:** 1.11.2
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the ChangeSet model and the gitexe implementation, then inspect the output of `git log --decorate` for how tagged commits are represented. The work is done when ChangeSet can optionally retain tag information for a commit and the gitexe path can populate it, with coverage for the parsed history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100