Seems like "Is this major breaking change?" does nothing (almost)

Open
#16 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
cli, release, tooling

Research direction

No files or tests are named. Start by tracing the commit-message wizard and validator behavior for breaking changes, then compare it with the semantic-release expectations described in the issue; done means the prompt behavior is consistent and a major option is supported where appropriate.

Written by the indexing model from the issue text.

Description

question

More specifically said, it does, but that adding of BREAKING CHANGE to body and title seems almost useless. Or at least not make sense to output that prompt every time for every kind of type.

Not to mention that the wizard (the prompts) doesn't have break / major and etc. It would be good to at least have major because it seems that semantic-release don't care about the wordings, but care only about major type, which is awful, but anyway.

Dominant language
JavaScript
Stars
25
Forks
8
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bahmutov/simple-commit-message

All issues in bahmutov/simple-commit-message

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.