wanadev / changelogify Goto Github PK

• Do not write branch number if it is 0
• Handle case of branch name not starting with a number
• make clear that the branch number is the default number to link changelog entry to an issue url
• do not ask for branch number if specified in config

To conform with prettier and other tools that maintain code styling, allowing configuration of the tab size would be really nice.

Alternatively or additionally respect .editorconfig settings.

• lint
• divide code into sub-files

Hi,

We could add a new changelog type for developments related to tests, as they are not really "Meta" nor "Added" (this one being more related to new features).

In order to process changelogify during npm version, npm run changelogify -- release -s must be synchronous

Error if changelog executed in detached head git state. Should be handled by a defensive check

Would be handy to have the command "add" as default.

Create an entry in the configuration file to do so.

Release should not throw an error if there's no changelogs.
Il should only add a new version line un CHANGELOG.md with no change

{ Error: ENOENT: no such file or directory, scandir '/home/jbghoul/dev/kazaplan-plugin-model-thumbnailer/changelogs/unreleased/'
    at Object.readdirSync (fs.js:790:3)
    at Command.release (/home/jbghoul/dev/kazaplan-plugin-model-thumbnailer/node_modules/changelogify/index.js:211:31)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  errno: -2,
  syscall: 'scandir',
  code: 'ENOENT',
  path:
   '/home/jbghoul/dev/kazaplan-plugin-model-thumbnailer/changelogs/unreleased/' }

Step to reproduce:

• Add a changelog with no issue number
• Generate a changelog release
• There is 2 lines for the same changelog entry:

### Fixed
- Fix changelog
- Fix changelog - [](https://github.com/wanadev/changelogify/issues/)

version 1.2.1

see https://github.com/wanadev/enlightme for an example

If an update brings new configuration lignes in config.js, it requires to use changelogify init to write it locally.

This should be handled automatically to ease the use and avoid errors

If an update brings new configuration lignes in config.js, it requires to use changelogify init to write it locally.

This should be handled automatically to ease the use and avoid errors

If an update is made, it sometimes require to execute changelogify init to copy new configuration lines.

This should be detected and prompted to the user.