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

[feat] Introduce NewRelease.DiscussionCategoryName, Fixes #2746 #2842

Merged
merged 2 commits into from Jan 2, 2024

Conversation

AndreyAkinshin
Copy link
Contributor

In this PR, we introduce the support of discussion_category_name for new releases:

discussion_category_name string
If specified, a discussion of the specified category is created and linked to the release. The value must be a category that already exists in the repository. For more information, see "Managing categories for discussions in your repository."

This parameter was introduced in GitHub REST API 2022-11-28, see https://docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#create-a-release

Resolves #2746

@nickfloyd nickfloyd added the Type: Feature New feature or request label Jan 2, 2024
Copy link
Contributor

@nickfloyd nickfloyd left a comment

Choose a reason for hiding this comment

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

Thank you for the commits here! ❤️

@nickfloyd nickfloyd merged commit 48d061a into octokit:main Jan 2, 2024
5 checks passed
@AndreyAkinshin AndreyAkinshin deleted the discussion_category_name branch January 2, 2024 23:32
AndreyAkinshin added a commit to dotnet/BenchmarkDotNet that referenced this pull request Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature New feature or request
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[FEAT]: Add discussion_category_name to create release payload
2 participants