docs: update http to https in license link

[AshwiniBokka]

First-time contributed to Apache TVM.

Changes:

• Updated HTTP to HTTPS in license link in README.md for better security

Why:

• HTTPS provides encryption and integrity
• Apache Foundation recommends HTTPS
• Minor improvement but follows best practices

Signed-off-by: Ashwini Bokka

[gemini-code-assist]

Summary of Changes

Hello @AshwiniBokka, 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 implements a minor but significant security improvement by upgrading the Apache license link within the README.md file from an insecure HTTP protocol to a secure HTTPS protocol. This change enhances data integrity and encryption when accessing the license information, adhering to modern web security standards and Apache Foundation recommendations.

Highlights

• Security Enhancement: The license link in README.md has been updated from HTTP to HTTPS to ensure encrypted and secure access, aligning with best practices.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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

Thank you for this contribution. Updating the license link in README.md from HTTP to HTTPS is a good security improvement. The change is correct and follows best practices.

To make this change more comprehensive, I'd suggest also updating the http links to https in the LICENSE file. I noticed similar http://www.apache.org/licenses/ links on lines 3 and 195 of that file. Applying the same update there would make your contribution even more complete.

[cchung100m]

LGTM, Thanks to @AshwiniBokka

Please re-run the CI after fixing the failed: PR body must not tag anyone but found these usernames: ['@gmail']

[AshwiniBokka]

@tvm-bot please run ci

[AshwiniBokka]

@gemini-code-assist @cchung100m Thanks for catching this! I've updated the LICENSE file as suggested, changing http to https on lines 3 and 195. All requested changes are now complete.

[gemini-code-assist]

Thanks for the update, @AshwiniBokka! I've reviewed the changes and confirmed that the LICENSE file (lines 3 and 195) and README.md (line 9) have been successfully updated from HTTP to HTTPS. This is a great improvement for security and best practices. Much appreciated for addressing this so quickly!

[cchung100m]

Hi @AshwiniBokka

Thanks prompt reply. we still encounter lint error and please recheck the change, thanks.

[AshwiniBokka]

@tvm-bot please run ci

[AshwiniBokka]

@tvm-bot please run ci

[AshwiniBokka]

@cchung100m I've exhaustively verified this PR:

Changes Made:

1. README.md: http→https on line 9 (+1 byte, verified)
2. LICENSE: http→https on lines 3 & 195
3. CONTRIBUTORS.md: Added missing trailing newline (fixed whitespace lint)

Verification:

• git diff shows only the 3 intended changes
• Byte comparison confirms only 's' character added in README.md
• All files have Unix line endings (0 Windows CR)

The ASF header check continues to fail despite correct changes. Could you please:
a) Run check_asf_header.sh --fix to auto-correct any CI issue, or
b) Merge this minimal security improvement?

This has been blocking for 24+ hours despite correct implementation.

[AshwiniBokka]

@tvm-bot please run ci