-
Notifications
You must be signed in to change notification settings - Fork 10.8k
patch e2e vnext #8767
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
patch e2e vnext #8767
Conversation
Summary of ChangesHello @mattKorwel, 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 significantly enhances the end-to-end automation of the patch release process. It introduces new scripts to manage the entire lifecycle, from validating release channels and dynamically naming hotfix branches to triggering the release workflow and providing comprehensive status updates directly on the original pull request. The changes aim to make patch releases more robust, transparent, and user-friendly by connecting various stages of the release pipeline. Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this 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 refactors the patch release process into separate, more testable scripts, which is a great improvement for maintainability. My review focuses on improving the robustness of these new scripts. I've identified a critical bug that could cause incorrect release status reporting, an inefficient API usage pattern that could lead to performance issues, and a piece of redundant code. Addressing these points will make the new patch process more reliable.
|
Size Change: -2 B (0%) Total Size: 17.3 MB ℹ️ View Unchanged
|
| } | ||
|
|
||
| // Try to find the original PR that requested this patch | ||
| let originalPr = null; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't this cause silent failures if for some reason we didn't find a pr number
| description: 'The head ref of the merged hotfix PR to trigger the release for (e.g. hotfix/v1.2.3/cherry-pick-abc).' | ||
| required: true | ||
| type: 'string' | ||
| workflow_ref: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we add pull-requests: write to both release-patch-2-trigger.yml and release-patch-3-release.yml
Code Coverage Summary
CLI Package - Full Text ReportCore Package - Full Text ReportFor detailed HTML reports, please see the 'coverage-reports-22.x-ubuntu-latest' artifact from the main CI run. |
TLDR
Connect the dots end 2 end
Dive Deeper
More testable, ditch inline scripts