We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For our publish workflow: https://github.com/storyprotocol/gha-workflows/blob/main/.github/workflows/reusable-create-release.yml
Let's make use of proper labeling for better release notes,Since we're using https://github.com/mikepenz/release-changelog-builder-action?tab=readme-ov-file#setup
lets go through the settings and Action inputs to see if we can format it better, this also requires us to label our releases properly.
see the following for example:
- name: "Complex Configuration" id: build_changelog if: startsWith(github.ref, 'refs/tags/') uses: mikepenz/release-changelog-builder-action@{latest-release} with: configuration: "configuration_complex.json" owner: "mikepenz" repo: "release-changelog-builder-action" ignorePreReleases: "false" fromTag: "0.3.0" toTag: "0.5.0" token: ${{ secrets.PAT }}
See sample configuration_complex.json
configuration_complex.json
{ "categories": [ { "title": "## 🚀 Features", "labels": ["feature"] }, { "title": "## 🐛 Fixes", "labels": ["fix"] }, { "key": "tests", "title": "## 🧪 Tests", "labels": ["test"] }, { "title": "## 🧪 Tests and some 🪄 Magic", "labels": ["test", "magic"], "exclude_labels": ["no-magic"], "exhaustive": true, "exhaustive_rules": "false", "empty_content": "- no matching PRs", "rules": [ { "pattern": "open", "on_property": "status", "flags": "gu" } ] } ], "ignore_labels": [ "ignore" ], "sort": { "order": "ASC", "on_property": "mergedAt" }, "template": "#{{CHANGELOG}}\n\n<details>\n<summary>Uncategorized</summary>\n\n#{{UNCATEGORIZED}}\n</details>", "pr_template": "- #{{TITLE}}\n - PR: ##{{NUMBER}}", "empty_template": "- no changes", "label_extractor": [ { "pattern": "(.) (.+)", "target": "$1", "flags": "gu" }, { "pattern": "\\[Issue\\]", "on_property": "title", "method": "match" } ], "duplicate_filter": { "pattern": "\\[ABC-....\\]", "on_property": "title", "method": "match" }, "reference": { "pattern": ".*\\ \\#(.).*", "on_property": "body", "method": "replace", "target": "$1" }, "transformers": [ { "pattern": "[\\-\\*] (\\[(...|TEST|CI|SKIP)\\])( )?(.+?)\n(.+?[\\-\\*] )(.+)", "target": "- $4\n - $6" } ], "trim_values": false, "max_tags_to_fetch": 200, "max_pull_requests": 200, "max_back_track_time_days": 365, "exclude_merge_branches": [ "Owner/qa" ], "tag_resolver": { "method": "semver", "filter": { "pattern": "api-(.+)", "flags": "gu" } }, "base_branches": [ "dev" ] }
The text was updated successfully, but these errors were encountered:
DonFungible
No branches or pull requests
For our publish workflow: https://github.com/storyprotocol/gha-workflows/blob/main/.github/workflows/reusable-create-release.yml
Let's make use of proper labeling for better release notes,
Since we're using https://github.com/mikepenz/release-changelog-builder-action?tab=readme-ov-file#setup
lets go through the settings and Action inputs to see if we can format it better, this also requires us to label our releases properly.
see the following for example:
See sample
configuration_complex.json
The text was updated successfully, but these errors were encountered: