Search results

Allow any characters after <code>BREAKING CHANGE: </code>

bugUnintended behaviour in any area of the appUnintended behaviour in any area of the app

Status: Open.

#84 In octue/conventional-commits;

· cortadocodes opened on Jun 4, 2024

Add a description of how to document breaking changes

documentationImprovements or additions to documentationImprovements or additions to documentation

Status: Open.

#83 In octue/conventional-commits;

· thclark opened on Jan 7, 2024

TypeError on a PR with many commits

bugUnintended behaviour in any area of the appUnintended behaviour in any area of the app

Status: Open.

#74 In octue/conventional-commits;

· thclark opened on Aug 4, 2022

Consider merging some of the release notes sections

Status: Open.

#71 In octue/conventional-commits;

· cortadocodes opened on Jun 13, 2022

Consider putting all breaking changes at top of their sections in release notes generator

decision neededA decision is required (e.g. on UX or company policy)A decision is required (e.g. on UX or company policy)

Status: Open.

#59 In octue/conventional-commits;

· cortadocodes opened on Apr 5, 2022

Add support for <code>DEPRECATION</code> notes in commits

Status: Open.

#57 In octue/conventional-commits;

· cortadocodes opened on Mar 9, 2022

Write article on the benefits of conventional-commit-based continuous deployment on Medium for the new website

Status: Open.

#46 In octue/conventional-commits;

· cortadocodes opened on Nov 8, 2021

Link release note items to commit diff

Status: Open.

#43 In octue/conventional-commits;

· cortadocodes opened on Nov 1, 2021