feat(badges): Add option to exclude specific badges

[ioncakephper]

Introduce excludeBadges option to control which badges are generated.
This allows users to specify an array of badge keys to skip.

Update README:

• Utilize excludeBadges to remove 'npmVersion' and 'npmDownloads' badges.
• Move 'stars' and 'forks' badges from collapsed section to primary display.
• Update package.json description.

[gemini-code-assist]

Summary of Changes

Hello @ioncakephper, 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 enhances the markdown-magic-transform-badges utility by introducing a new excludeBadges configuration option. This feature empowers users to selectively omit specific badges from being generated, offering greater customization. The changes are accompanied by practical updates to the README, showcasing the new exclusion capability and improving the overall presentation of badges, alongside a more descriptive package.json entry.

Highlights

• New Feature: Exclude Badges Option: Introduced an excludeBadges option that allows users to specify an array of badge keys to prevent them from being generated, providing more control over the displayed badges.
• README Updates: The project's README has been updated to demonstrate the new excludeBadges option by removing 'npmVersion' and 'npmDownloads' badges. Additionally, 'stars' and 'forks' badges have been moved from the collapsed section to the primary display for better visibility.
• Package Metadata Enhancement: The package.json description has been updated to provide a clearer and more informative summary of the package's purpose.

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 introduces a useful excludeBadges option to allow users to selectively omit badges from the generated output. The implementation is clear, and the documentation in README.md has been updated to reflect this new feature. I've identified a high-severity issue with a debugging console.log statement that should be removed, and a medium-severity suggestion to clean up some commented-out code for better maintainability. Overall, this is a good addition.

[gemini-code-assist]

This console.log statement and the following blank line appear to be for debugging purposes. They should be removed before merging to avoid polluting the console output for users of this package.

[gemini-code-assist]

These lines are commented out. If this configuration is not planned for immediate implementation, it's best to remove this code to keep the codebase clean and avoid confusion about supported features.