You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user I want to see, what has changed in the current release of a Sketch plugin before installing it. For that I can refer to the "embedded changelog" feature of the appcast.xml, to a CHANGELOG file inside the plugin repository or to the page of each release on GitHub.
As a developer I'd like skpm to automatically generate changelog entries based on the commits created between the new release and the prior release upon publishing the new release. Commits should only be enclosed in the changelog if the commit message sticks to the [conventional commits specification].
The changelog should be added to a repository-local CHANGELOG file, to the release comment on GitHub and to the Appcast.xml file.
The text was updated successfully, but these errors were encountered:
possibly yes, but for now there wouldn't be much value and there are already tons of tools to generate a changelog. You could totally use one of them at the same time as skpm
As a user I want to see, what has changed in the current release of a Sketch plugin before installing it. For that I can refer to the "embedded changelog" feature of the appcast.xml, to a CHANGELOG file inside the plugin repository or to the page of each release on GitHub.
As a developer I'd like skpm to automatically generate changelog entries based on the commits created between the new release and the prior release upon publishing the new release. Commits should only be enclosed in the changelog if the commit message sticks to the [conventional commits specification].
The changelog should be added to a repository-local CHANGELOG file, to the release comment on GitHub and to the Appcast.xml file.
The text was updated successfully, but these errors were encountered: