-
Notifications
You must be signed in to change notification settings - Fork 320
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
[Feature]: #175
Comments
i dont undertand you bro :) |
I'll try to explain myself better https://github.com/icoretech/airbroke/commits/main as you can see I'm using opencommit for the vast majority of the commits. there are github actions, such as this one (https://github.com/icoretech/airbroke/blob/main/.github/workflows/generate-release.yml#L16) that can generate a changelog (and even determine version bumps) by looking at the opencommits done between tags. however as you can also see it's kinda hit and miss: icoretech/airbroke@v1.1.12...v1.1.13 expand the first commit and you'll see that the description is gigantic, but it's not making its way into the changelog. so I found the page I linked in the original ticket https://github.com/googleapis/release-please/tree/main#what-if-my-pr-contains-multiple-fixes-or-features |
Stale issue message |
Description
I'm using release please which has its way to parse commits for changelog: https://github.com/googleapis/release-please/tree/main#what-if-my-pr-contains-multiple-fixes-or-features
do you think we can modify the prompt to emit this kind of structured output?
Suggested Solution
modify the prompt to emit this kind of structured output
Alternatives
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: