The Wayback Machine - https://web.archive.org/web/20210829090651/https://github.com/topics/conventional-commits
Skip to content
#

conventional-commits

Here are 218 public repositories matching this topic...

opensource
tunnckoCore
tunnckoCore commented Feb 9, 2018

Which will behave like that

let settings = await prettyConfig('rollup', { configFiles })

if (!settings) {
  settings = await prettyConfig('rolldown', { configFiles })
}
console.log(settings)

instead of above we can hide it to look like that

const settings = await prettyConfig(['rollup', 'rolldown'], { configFiles })

if (!settings) {
  console.log('no config file
xsc27
xsc27 commented Jun 28, 2021

The action appears to exit 0 even when an expectation is thrown. (I forgot to checkout the repo, so the root cause is "user error". The action should still not exit 0 and allow CI to continue.)

Run TriPSs/conventional-changelog-action@v3
  with:
    github-token: ***
    skip-commit: true
    git-message: chore(release): {version}
    git-user-name: Conventional Changelog Action
    gi
oknozor
oknozor commented Mar 2, 2021

Is your feature request related to a problem? Please describe.
The current generated version commit is rather empty and it would be nice to have a changelog summary instead of an empty commit message.

Describe the solution you'd like
A straight forward way to implement this would be to have the cog changelog command output as the version commit message.

Additional context

Improve this page

Add a description, image, and links to the conventional-commits topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the conventional-commits topic, visit your repo's landing page and select "manage topics."

Learn more