Skip to content

Add GitHub Actions workflow for NodeJS with Webpack#14675

Closed
HLAINGMYOOO wants to merge 4 commits intogoogle-gemini:mainfrom
HLAINGMYOOO:main
Closed

Add GitHub Actions workflow for NodeJS with Webpack#14675
HLAINGMYOOO wants to merge 4 commits intogoogle-gemini:mainfrom
HLAINGMYOOO:main

Conversation

@HLAINGMYOOO
Copy link

@HLAINGMYOOO HLAINGMYOOO commented Dec 7, 2025

Summary

Details

Related Issues

How to Validate

Pre-Merge Checklist

  • Updated relevant documentation and README (if needed)
  • Added/updated tests (if needed)
  • Noted breaking changes (if any)
  • Validated on required platforms/methods:
    • MacOS
      • npm run
      • npx
      • Docker
      • Podman
      • Seatbelt
    • Windows
      • npm run
      • npx
      • Docker
    • Linux
      • npm run
      • npx
      • Docker

@HLAINGMYOOO HLAINGMYOOO requested a review from a team as a code owner December 7, 2025 07:57
@google-cla
Copy link

google-cla bot commented Dec 7, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@gemini-code-assist
Copy link
Contributor

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

@HLAINGMYOOO HLAINGMYOOO requested a review from a team as a code owner December 13, 2025 18:13
@jackwotherspoon
Copy link
Contributor

Hi @HLAINGMYOOO 👋

Without a PR description properly describing the contribution and why it is needed we can't move forward with reviewing this. Can you provide details and an explanation of the changes and why this is needed?

Also we require contributors to sign the CLA, looks like that is missing as well.

Thanks!

@jackwotherspoon
Copy link
Contributor

Hi @HLAINGMYOOO please add a detailed PR description outlining what this is solving and why so we can prioritize a review.

Without this information we may have to close the PR.

@gemini-cli gemini-cli bot added status/need-issue Pull requests that need to have an associated issue. priority/p1 Important and should be addressed in the near term. and removed status/need-issue Pull requests that need to have an associated issue. labels Jan 7, 2026
@bdmorgan
Copy link
Collaborator

Hi @HLAINGMYOOO, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this.

We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines.

Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed.

Thank you for your understanding and for being a part of our community!

@gemini-cli
Copy link
Contributor

gemini-cli bot commented Jan 24, 2026

Hi there! Thank you for your contribution to Gemini CLI.

To improve our contribution process and better track changes, we now require all pull requests to be associated with an existing issue, as announced in our recent discussion and as detailed in our CONTRIBUTING.md.

This pull request is being closed because it is not currently linked to an issue. You can easily reopen this PR once you have linked it to an issue.

How to link an issue:
Add a keyword followed by the issue number (e.g., Fixes #123) in the description of your pull request. For more details, see the GitHub Documentation.

Thank you for your understanding and for being a part of our community!

@gemini-cli gemini-cli bot closed this Jan 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority/p1 Important and should be addressed in the near term.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants