fix: prevent duplicate PR entries in release notes

[Nishika10]

…d PR entries

Description

This PR fixes #851

Notes for Reviewers
This PR adds no-duplicate-categories: true to the release-drafter configuration (.github/release-drafter.yml).

Signed commits

• Yes, I signed my commits.

[gemini-code-assist]

Summary of Changes

Hello @Nishika10, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an issue where release notes were incorrectly displaying duplicate entries for pull requests. By modifying the release-drafter configuration, it ensures that each pull request is listed only once, leading to more accurate and streamlined release documentation.

Highlights

• Release Notes Configuration: Introduced no-duplicate-categories: true in the .github/release-drafter.yml file to prevent pull request entries from appearing multiple times in the generated release notes.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the release-drafter.yml configuration to prevent duplicate entries in the release notes. The addition of no-duplicate-categories: true is the correct way to ensure that a pull request appears in only one category, even if it has multiple labels corresponding to different categories. The change is simple, effective, and correctly placed. I have no further suggestions.

[welcome]

Thanks for your contribution to Meshery! 🎉

        Join the community, if you haven't yet and please leave a ⭐ star on the project. 😄

[leecalcote]

Good work! If you haven't joined the Layer5 Community Slack, yet, I invite you to jump in.