With datasources=issues and the following GItHub Actions workflow, a Release Note has all issues with no error.
Then, run the workflow again, the Release Note gets expected issues, that have closed between the last tag and the latest tag.
name: Releaseon:
push:
tags:
- "*"jobs:
note:
name: Releaseruns-on: ubuntu-lateststeps:
- name: Checkoutuses: actions/checkout@v3.5.3with:
fetch-depth: 0
- name: Use Node.jsuses: actions/setup-node@v3.8.0
- name: Install grenrun: | npm install github-release-notes -g - name: Create a releaseenv:
GREN_GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}'run: | gren release \ --override \ --tags=${{ github.ref_name }}.grenrc.yaml is here.
---
dataSource: "issues"groupBy:
"✨ Enhancement":
- "enhancement""🐛 Bug":
- "bug"changelogFilename: "CHANGELOG.md"template:
label: ""limit: 99
With
datasources=issuesand the following GItHub Actions workflow, a Release Note has all issues with no error.Then, run the workflow again, the Release Note gets expected issues, that have closed between the last tag and the latest tag.
.grenrc.yamlis here.