-
-
Notifications
You must be signed in to change notification settings - Fork 5
Closed
Labels
needs-infoFurther information is requestedFurther information is requested
Description
So there are a number of issues I hit when just trying to test this, so constructively I figured I would lay them out here.
- When initially trying to use the package and run
artisan changelog:addit fails with a folder creation error. This seems to be due to both.changesand.changes/unreleasednot already existing and after manually adding the whole folder structure, it added an xml changelog. - When trying to generate a release, I ran
changelog:release, and that worked but no changelog was generated. This was confusing and I had to runchangelog:generateseparately just to get a changelog added. - Following the last step, the changelog didn't have any content other than the release version I had specified, and the tagline about being generated by this package.
- On a subsequent attempt to run
changelog:addI was hit by another folder creation error and that's about where I stopped.
Here is the whole command list I ran to get to this point:
mkdir .changes
mkdir .changes/unreleased
artisan changelog:add -v --type=added --message "add new feature"
artisan change:list # This list just said unreleased without the change I had just added
artisan changelog:release 5.15.0
artisan changelog:generate
Contents of the generated CHANGELOG.md:
# Release Notes
## [5.15.0]
This file was generated by [markwalet/laravel-changelog](https://github.com/markwalet/laravel-changelog)
It's potentially worth noting that I'm using the gitflow workflow, so the branch I am on is in the format of feature/<TICKET> as I wonder if the nesting is causing an issue.
OH and one last thing, I already had a changelog in place which this command overwrote so it's also worth noting that you can't use this with an already present CHANGELOG.md
Metadata
Metadata
Assignees
Labels
needs-infoFurther information is requestedFurther information is requested