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
conventional-release action does not seem to add release body when changes were marked by docs and build (maybe something else) types. I understand why "build" changes are not making to the release description but changes marked with "docs" seem like a useful thing to have there.
Please clarify if this is by design or not. If this is by design, any chance to get the compleat list of conventional tags that make it into the release documentation?
conventional-release action does not seem to add release body when changes were marked by docs and build (maybe something else) types. I understand why "build" changes are not making to the release description but changes marked with "docs" seem like a useful thing to have there.
Please clarify if this is by design or not. If this is by design, any chance to get the compleat list of conventional tags that make it into the release documentation?
Example of release that was produced by merging a PR with "docs" changes - https://github.com/extenda/hiiretail-item-input-api/releases/tag/v2.6.5
PR itself: https://github.com/extenda/hiiretail-item-input-api/pull/105
The text was updated successfully, but these errors were encountered: