conventional-commits

Description

A config option to include an additional question at the end of cz commit that displays the DCO and asks if the committer agrees to the DCO and, if yes, appends the line Signed-off-by: [NAME] <[EMAIL]> at the end of the commit message. [NAME] and [EMAIL] would be pulled from git config.

Possible Solutions

1. See description.
2. I suppose this could also be done inst

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

Actually, the logging is made by standard version, we should first disable it and log ourself the following events:

• bump version from {from} to {to}
• output changes in {projectRoot}/{path-to-changelog}.md
• commit created
• tag {tag} created
• push success (if git push occurred)
• run postTargets {postTargets}
• postTarget {postTargetName} failure
• postTarget `{postTarge

Is there a way to skip doing the Git Pull?
I always ensure that I do a checkout with all history and branches so I do not need the extra pull.
It is actually quite harmful where I want to be able to build my commit on a merge to main and then tag and release using this action.
However if someone else merges

Is your feature request related to a problem? Please describe.
cog edit is not suited for repository that has not been following the conventional commit from the start.

Describe the solution you'd like
Allowing to edit commit from latest tag only would make it usable on a daily basis. Before push our code to remote or rebasing some changes etc.

cog edit --from-l

Currently commitsar defaults to master branch. Given the recent changes by Github it would be good to also default to main, unless specified differently in .commitsar.yml

Maybe it's just a quirk on my machine 🤔

Describe the solution you'd like
Same as #59 with GitHub provider

related to #50