Comments (5)
Have you merged main
into your branch? The commit messages are picked straight from the git log up until the latest tag. If that tag isn't present on the branch, it'll pick up more commits than it should.
from conventional-commits.
Also which repo is this occurring for you on?
from conventional-commits.
This may be solved by #17
from conventional-commits.
Image to clarify what I mean. I’ve not checked if this is solved yet but I think perhaps not since the feature/epic branch wouldn’t have a tag after Commit 2 in this diagram?
from conventional-commits.
I think what will happen at the moment is that:
feature/epic
will have commits 1 and 2 in its PR descriptionfeature/sub
will have commits 1, 2, 3, and 4 in its PR description- When
feature/sub
is merged intofeature/epic
,feature/epic
's PR description will then contain commits 1, 2, 3, and 4 - When
feature/epic
is then merged intomain
, the release notes will contain commits 1, 2, 3, and 4
I guess what we want is the above except that feature/sub
should only have commits 3 and 4 in its PR? I think I can update the code to do this.
from conventional-commits.
Related Issues (20)
- Mkver comparison incorrect where package.json not in repository root HOT 3
- Missing commits from PR history
- Add style subheading to release notes
- Add whitespace to valid commit header endings
- Add commit codes for deprecation and subsequent removal HOT 3
- Add support for `DEPRECATION` notes in commits
- Implement a set of Github Actions
- Consider putting all breaking changes at top of their sections in release notes generator
- Consider using ❌ or similar emoji to denote breaking changes HOT 4
- Allow brackets at end of commit message
- BREAKING-CHANGES has a mismatched format HOT 1
- Add breaking change commit notes to release notes HOT 3
- I want a boom
- Remove line length limit for commit bodies or format it away so upgrade instructions render nicely in markdown
- Improve upgrade instructions format in release notes generator
- Consider merging some of the release notes sections
- TypeError on a PR with many commits HOT 2
- Ignore commit header line length limit if commit code is `MRG`
- Remove old scripts
- Add a description of how to document breaking changes
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from conventional-commits.