-
Notifications
You must be signed in to change notification settings - Fork 26
chore : add changelog to makefile #227
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
chore : add changelog to makefile #227
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #227 +/- ##
===========================================
- Coverage 56.29% 56.23% -0.06%
===========================================
Files 41 41
Lines 1796 1796
===========================================
- Hits 1011 1010 -1
- Misses 785 786 +1
Flags with carried forward coverage won't be shown. Click here to find out more. see 1 file with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Issue number: #217
Summary
Changelog was not being generated because there was no action in Makefile for changelog.
This Makefile is called from the GitHub action
Build and publish latest changelog
https://github.com/awslabs/aws-lambda-powertools-dotnet/blob/develop/.github/workflows/reusable_publish_changelog.ymlChanges
User experience
Changelog will be updated on release
Checklist
Please leave checklist items unchecked if they do not apply to your change.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.