-
Notifications
You must be signed in to change notification settings - Fork 62
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
Create Prepare Release workflow #370
Conversation
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.
Looks good besides that one comment.
scripts/release_notes_generator.py
Outdated
def _create_release_notes(issues_by_category, version, date): | ||
title = f'## v{version} - {date}' | ||
release_notes = f'{title}{NEW_LINE}{NEW_LINE}' | ||
for category in ISSUE_LABELS + ['misc']: |
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.
SDV-Enterprise uses another list here.
It also has this extra line:
# Filter our PRs
issues_on_page = [issue for issue in issues_on_page if issue.get('pull_request') is None]
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.
@R-Palazzo do these changes need to be propagated to any other libraries?
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.
Good catch, thanks @fealho.
Yes, if we want to use what's in Enterprise, SDMetrics and SDGym must be updated (other libraries already have the changes)
I have a PR on both libraries that are related so I will include the changes @amontanez24
CU-86b2xrf9c
Resolve #364