mathieudutour / mathieudutour/github-tag-action
Commit parsing does not work for squash commits
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 733
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
It would be a really nice feature if the parsing handled commits squashed by github. Seemingly the only way to get it working is either a merge commit or rebase merge but convention (at least where I work) is to squash features so master doesn't get too messy after a while.
This would mean links in the release doc don't point to one commit, but the merge commit. Although the release doc sections and version bump amount would still work.
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 tracing the action's commit-parsing path and the release-document link generation described in the issue, focusing on how squash merges are identified. Confirm the existing merge and rebase behavior; done means release entries link to the squash merge commit while release sections and version-bump amounts still work.
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
- 42/100