Skip to content

[Docs] Update author from NeuralMagic to vLLM#2444

Open
kylesayrs wants to merge 2 commits intomainfrom
kylesayrs/update-author
Open

[Docs] Update author from NeuralMagic to vLLM#2444
kylesayrs wants to merge 2 commits intomainfrom
kylesayrs/update-author

Conversation

@kylesayrs
Copy link
Copy Markdown
Collaborator

No description provided.

Signed-off-by: Kyle Sayers <kylesayrs@gmail.com>
@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 4, 2026

👋 Hi! Thank you for contributing to llm-compressor. Please add the ready label when the PR is ready for review.

Note: This is required to complete the testing suite, please only add the label once the PR is code complete and local testing has been performed.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 primarily focuses on updating project metadata and documentation to reflect a transition in ownership or branding from Neuralmagic to the vLLM Project. The changes ensure that the project's setup.py and relevant documentation accurately represent the current maintainers and licensing details.

Highlights

  • Project Ownership Update: The author and author email in setup.py have been updated from 'Neuralmagic, Inc.' to 'The vLLM Project' and 'vllm-questions@lists.berkeley.edu' respectively, reflecting a change in project ownership or branding.
  • License Specification: The license in setup.py has been explicitly updated from 'Apache' to 'Apache 2.0' for clarity and precision.
  • Documentation Link Correction: A link to the compressed-tensors library in src/llmcompressor/modifiers/README.md has been updated to point to the vllm-project GitHub organization instead of neuralmagic.

🧠 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.

Changelog
  • setup.py
  • src/llmcompressor/modifiers/README.md
    • Updated the GitHub link for the compressed-tensors library to point to the vllm-project organization.
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.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the author information, license specification, and repository link to reflect the transition from NeuralMagic to vLLM, ensuring accurate project metadata and documentation. No vulnerabilities were found during the security review.

@dsikka dsikka added the ready When a PR is ready for review label Mar 30, 2026
@mergify mergify bot added the queued label Mar 30, 2026
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Mar 30, 2026

Merge Queue Status

  • Entered queue2026-03-30 21:38 UTC · Rule: default
  • Checks skipped · PR is already up-to-date
  • 🚫 Left the queue2026-03-30 21:39 UTC · at bd8e0aa0764818bdccef49b7de3079e385a7e76a

This pull request spent 11 seconds in the queue, including 1 second running CI.

Required conditions to merge
  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • check-success=DCO
  • check-success=base-tests (3.10)
  • check-success=base-tests (3.13)
  • check-success=markdown-link-check
  • check-success=pytorch-tests (3.10)
  • check-success=pytorch-tests (3.13)
  • check-success=quality-check
  • any of:
    • check-success=transformers-tests
    • check-neutral=transformers-tests
    • check-skipped=transformers-tests
  • any of [🛡 GitHub branch protection]:
    • check-success = DCO
    • check-neutral = DCO
    • check-skipped = DCO
  • any of [🛡 GitHub branch protection]:
    • check-success = transformers-tests
    • check-neutral = transformers-tests
    • check-skipped = transformers-tests
  • any of [🛡 GitHub branch protection]:
    • check-success = base-tests (3.10)
    • check-neutral = base-tests (3.10)
    • check-skipped = base-tests (3.10)
  • any of [🛡 GitHub branch protection]:
    • check-success = base-tests (3.13)
    • check-neutral = base-tests (3.13)
    • check-skipped = base-tests (3.13)
  • any of [🛡 GitHub branch protection]:
    • check-success = pytorch-tests (3.10)
    • check-neutral = pytorch-tests (3.10)
    • check-skipped = pytorch-tests (3.10)
  • any of [🛡 GitHub branch protection]:
    • check-success = pytorch-tests (3.13)
    • check-neutral = pytorch-tests (3.13)
    • check-skipped = pytorch-tests (3.13)
  • any of [🛡 GitHub branch protection]:
    • check-success = ready-label-check
    • check-neutral = ready-label-check
    • check-skipped = ready-label-check
  • any of [🛡 GitHub branch protection]:
    • check-success = markdown-link-check
    • check-neutral = markdown-link-check
    • check-skipped = markdown-link-check
  • any of [🛡 GitHub branch protection]:
    • check-success = quality-check
    • check-neutral = quality-check
    • check-skipped = quality-check

Reason

Pull request #2444 has been dequeued

The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. 2 of 9 required status checks have not succeeded: 1 expected. You're not authorized to push to this branch. Visit https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

@mergify mergify bot added dequeued and removed queued labels Mar 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dequeued ready When a PR is ready for review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants