mathieudutour / mathieudutour/github-tag-action
[HELP] [QUESTION] Pull request not generate changelog
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 733
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
hello,
First thank you for your amazing work!
I got a question, currently when i merge a pull request with lot's of commit tag-action not generate full change-log from commit message.It's possible to do it with your actions?
# Example
i created a branch, committed 6 times
```
fix: remove white page
fix: use router instead of window.location
feat: add electron logging
fix: sanitize payload to avoid xss
style: lint
docs: update readme
```
i created a pull request with the name:
`fix(desktop): auto update (#134)`
i merged my pull request with this commit message(default GitHub commit message when you merge a pr):
```
fix(desktop): auto update (#134)
* fix: remove white page
* fix: use router instead of window.location
* feat: add electron logging
* fix: sanitize payload to avoid xss
* style: lint
* docs: update readme
```
change log output:
> Bug Fixes
> desktop: autoupdate (#137) (20086ca)
# Actual Behavior
1. i create a branch named test
2. i commited multiple time with convential commit
3. on GitHub when merge my pr with default commit message (pr name + all commit message)
4. only first commit message working
# Wanted behavior
1. i create a branch named test
2. i committed multiple time with conventional commit
3. on GitHub when merge my pr with default commit message (pr name + all commit message)
4. i want to have a full changelog generated from pr commit message
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
Start by inspecting how the GitHub Action parses the merge commit message and selects changelog entries. Reproduce the example with multiple conventional commits, then verify that the generated changelog includes the requested fix, feat, style, and docs entries rather than only the pull request title.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, typescript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100