release icon indicating copy to clipboard operation
release copied to clipboard

Published 20 hours ago • verified publisher icon vercel

Support for feature branches

Open aesopwolf opened this issue 8 years ago • 4 comments

My team uses feature branches, and we also use the "Squash and merge" feature within GitHub. This makes our master branch look like this (by default):

image

So, do you think it would be possible for release to detect commit messages in that format (instead of using parenthesis such as Error logging works now (patch))? The Angular guidelines could be used:

listed under ### Minor Changes:

  • feat
  • feature

listed under ### Patches:

  • fix
  • docs
  • style
  • refactor
  • perf
  • test
  • chore

So anything that begins with those words would automatically be sorted to minor or patch.

aesopwolf avatar Jan 05 '17 05:01 aesopwolf

Hi dropping in from the @conventional-changelog team. We have many tools for parsing git commits, doing releases etc. with different formats. I personally am most familiar with the angular convention, but I'm pretty sure you can find useful stuff from us. E.g. Our core changelog generator that is used by both semantic-release and standard-version. Just gimme a holla if you want to know more.

Tapppi avatar Jan 07 '17 10:01 Tapppi

@Tapppi what do you guys use to detect breaking features? Or when you need to bump to the next MAJOR version number?

The most basic/naive solutions I can think of:

  1. Include "(major)" in the commit message. This is what release is currently doing
  2. Have the interactive CLI ask "Are there breaking changes in this release?"

I'm just wondering if there isn't a better/more-automated way though.

aesopwolf avatar Jan 08 '17 06:01 aesopwolf

@aesopwolf The angular convention dictates that breaking change commits should have a footer of BREAKING CHANGE: and the rest of the commit message is reserved for that change.

See the standard-version changelog for an example. So for example, the 4.0.0 has a bug fix

include merge commits in the changelog

and if you go to the commit linked to that change you'll find the BREAKING CHANGE that is included as the 4.0.0 breaking change

merge commits are now included in the CHANGELOG.

Docs on it can be found in the conventional-changelog-standard commit guidelines or in the more detailed angular docs linked there.

Tapppi avatar Jan 08 '17 13:01 Tapppi

Indeed, it would be great if we could setup release to use the conventional-changelog format.

tleunen avatar Jan 16 '17 14:01 tleunen