-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
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
attempt automated release notes #87
Conversation
Codecov Report
@@ Coverage Diff @@
## main #87 +/- ##
=======================================
+ Coverage 83.2% 83.5% +0.4%
=======================================
Files 6 6
Lines 1652 1652
Branches 420 420
=======================================
+ Hits 1374 1380 +6
+ Misses 227 218 -9
- Partials 51 54 +3
|
I'm up for trying it out. I think that this does not generate the changelog automatically though. It will give you a button to generate it manually afterward. There should be a way of using the generated changelog within the action, where we now pass the result of gitcount. |
This seems to do the trick on:
push:
tags:
- 'v*'
name: Create Release
jobs:
create-github-release:
name: Create GitHub Release
runs-on: ubuntu-latest
steps:
- name: Create Release Notes
uses: actions/github-script@v4.0.2
with:
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
await github.request(`POST /repos/${{ github.repository }}/releases`, {
tag_name: "${{ github.ref }}",
generate_release_notes: true
}); |
Good find on that. Does this mean that the |
Also, @martinfleis can you make a small PR to this repo top test for more contributors than myself? I know how to exclude authors in |
My understanding is that
Yes, we should be able to just replace the one we have.
Sure. |
I am going to merge this, then tag and cut a release. 99% sure it won't work on the first try, but got to start somewhere. |
Worked the first time!! 🥳 |
Nice! |
This PR attempts the adoption of automated release notes in
tigernet
prior to implementation inspaghetti
. See pysal/spaghetti#655 for details.