Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Include "refacto" and "chore" commits in releases created by semantic-release

See original GitHub issue

openwhyd.org is an open-source music platform used daily by thousands of users to create playlists of songs from the web (Youtube, Soundcloud, etc…), and discover musical gems from similar users.

Tech stack: Node.js, MongoDB, Docker, Mocka, Webdriver.io, jQuery, Electron + iOS app

Goal

semantic-release automatically creates a github release after commits are merged into master.

it automatically bumps the version number (major, minor, or patch) according to the commit message. (e.g. breaking, feat, fix, chore…)

it’s ok to not bump the version number for commits that do not have an impact for users (e.g. chore or refacto), but I would like them to still be listed in each github release.

solutions to be tried:

Howto

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

How to install, setup and run Openwhyd on your computer: INSTALL.md
How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Issue Analytics

State:
Created 5 years ago
Comments:22 (22 by maintainers)

Top GitHub Comments

1reaction

Brawrdoncommented, Oct 9, 2018

No, the commit would have to be something like:

chore(scope): subject
CHORE:

Message about breakage here

The semi colon is important too

1reaction

Brawrdoncommented, Oct 9, 2018

I think semantic-release isn’t updating because I’m doing it locally, I noticed the fact it automatically does a “dry run”.

I think I solved it! Placing BREAKING CHANGE into the footer of commits (after some more configuration) would solve the problem. Stumbling upon this changelog, it seems to be using the default configurations; angular preset and so on. However, when looking at the commits labeled as chore and refactoring, they both have BREAKING CHANGES at the start of their header.

I’m now looking to see if it would work by changing noteKeywords!