Skip to content
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

Release notes should not include PRs #2083

Merged
merged 3 commits into from
Jun 21, 2024
Merged

Conversation

amontanez24
Copy link
Contributor

resolves #2074

This PR also changes the order that each category appears in for the release notes to put features and customer issues at the top

@amontanez24 amontanez24 requested a review from a team as a code owner June 20, 2024 15:34
@amontanez24 amontanez24 requested review from rwedge and removed request for a team June 20, 2024 15:34
Co-authored-by: Gaurav Sheni <gvsheni@gmail.com>
@@ -23,6 +23,14 @@
'feature request',
'customer success',
]
ISSUE_LABELS_ORDERED_BY_IMPORTANCE = [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be better to just change the order of ISSUE_LABELS to match what you want, rather than creating a new global variable?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The other one is a different order because when picking which category to assign a label to, I want the order to be different. For example, if an issue is labeled both a feature request and internal, I want it to be only put in the internal category of the release notes. So the order for ISSUE_LABELS is intentionally different

@amontanez24 amontanez24 merged commit 36a5619 into main Jun 21, 2024
39 checks passed
@amontanez24 amontanez24 deleted the issue-2074-release-notes-prs branch June 21, 2024 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Release notes should not include PRs
3 participants