Update the RPM URI to refer to GitHub, not RedHat.

[RokeJulianLockhart]

Updates the RPM specification URI to refer to this GitHub repository, rather than RedHat. I don't know whether a “Bug URL” key would also be useful.

[gemini-code-assist]

Summary of Changes

Hello @RokeJulianLockhart, 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 updates the virtio-win.spec file to correctly reflect the project's official repository. The change ensures that the URL metadata embedded in the RPM package points to the GitHub location where the virtio-win-pkg-scripts project resides, rather than a generic Red Hat website. This improves the accuracy and relevance of the package's descriptive information.

Highlights

• RPM Spec File Update: The URL field within the virtio-win.spec file has been updated to point to the project's GitHub repository, https://github.com/virtio-win/virtio-win-pkg-scripts, replacing the previous Red Hat URL.

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 URL in the virtio-win.spec file to point to the project's GitHub repository instead of a generic RedHat URL. This is a good improvement for clarity. I've also suggested adding a BugURL to point to the GitHub issues page, as you mentioned in the description, which would be a helpful addition for users.

[gemini-code-assist]

This is a good change to point to the correct project repository. As you mentioned in the PR description, adding a BugURL would indeed be useful. It helps users easily find where to report issues. You can add it right after the URL line to point to the repository's issue tracker.

URL: https://github.com/virtio-win/virtio-win-pkg-scripts
BugURL: https://github.com/virtio-win/virtio-win-pkg-scripts/issues

[RokeJulianLockhart]

It's more useful when the domain of each URI differs. I don't see much value in having both when /issues is so trivial to locate.

[kostyanf14]

I agree to ignore this comment.