title: Many conventional commits of type feat on one feature branch
body: <p>I've been added to a repo which uses <a href="/questions/tagged/semantic-release" class="post-tag" title="show questions tagged &#39;semantic-release&#39;" rel="tag">semantic-release</a> to automate bumping up the version of the NPM package. The repo uses the <a href="https://www.conventionalcommits.org/en/v1.0.0/" rel="nofollow noreferrer">Conventional Commits specification</a> and has a very limited README.</p>
  <p>If I was to create a <code>feature/ABC-123</code> branch which contains a new feature, does that mean every single commit I make should have a commit structure of <code>feat: my message related to this commit</code> or should I only have 1 <code>feat</code> commit and the rest <code>chore</code> or another type which does not bump up the version of the repo?</p>
  <p>Or do I not need to worry about that as the branch is <code>feature/ABC-123</code> and therefore <a href="/questions/tagged/semantic-release" class="post-tag" title="show questions tagged &#39;semantic-release&#39;" rel="tag">semantic-release</a> knows to bump the package up by 1 minor version as it's in a feature folder?</p>
  <p>Hopefully the above makes sense, but if not here is a commit history example:</p>
  <pre><code>feat: add product card basic layout
  feat: add title to product card
  test: add unit tests to product card
  feat: add image to product card
  chore: update breakpoints for card
  test: add more unit tests
  </code></pre>
  <p>Would this example above bump the NPM package up by 3 minor versions as I've used <code>feat</code> 3 times, or one it only bump by 1 minor version? Or does this not matter and the only thing that matter is squashing the commits and ensuring <code>feat: added product card</code> for example is the squashed commit message?</p>