-
Notifications
You must be signed in to change notification settings - Fork 1
feat: Improve fail progress message #64
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
Conversation
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.
Hello @koki-develop, 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!
Summary of Changes
This pull request enhances the error handling and progress reporting in the build and install processes. Specifically, it introduces a fail status to the progress indicator, allowing users to see which workflows or actions failed during the build or install process. The changes also involve refactoring the import paths for getFileContent and getCommit to use the ../lib/github path instead of ../../internal/git.
Highlights
- Error Handling: The pull request adds a
try...catchblock around the_buildWorkflowcall inlib/cli/build/index.tsxto catch errors and report them using the newfailstatus in the progress indicator. - Progress Reporting: A
failstatus is added to the progress indicator inlib/cli/ui/Progress.tsxto visually indicate when a build or install step has failed. - Import Path Refactoring: The pull request updates import paths for
getFileContentandgetCommitinlib/cli/install/action-yaml.tsandlib/cli/install/commit.tsto use../lib/github. - Install Process Error Handling: The pull request adds a
try...catchblock around the action installation logic inlib/cli/install/index.tsxto catch errors and report them using the newfailstatus.
Changelog
Click here to see the changelog
- lib/cli/build/index.tsx
- Added a
try...catchblock to handle errors during workflow building. - Introduced the
failfunction from the progress indicator to report failed workflows.
- Added a
- lib/cli/install/action-yaml.ts
- Updated the import path for
getFileContentto../lib/github.
- Updated the import path for
- lib/cli/install/commit.ts
- Updated the import path for
getCommitto../lib/github.
- Updated the import path for
- lib/cli/install/index.tsx
- Added a
try...catchblock to handle errors during action installation. - Introduced the
failfunction from the progress indicator to report failed actions.
- Added a
- lib/cli/install/type-def.ts
- Updated the import path for
toUpperCamelCaseto../lib/util.
- Updated the import path for
- lib/cli/ui/Progress.tsx
- Added a
failstatus to theProgressStatustype. - Implemented visual representation for the
failstatus using a red '✗' symbol. - Added a
failfunction to the progress indicator to trigger thefailstatus.
- Added a
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| 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 issue 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 is currently in preview and 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 to provide feedback.
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.
A red 'X' now appears,
When builds crash down in tears,
Progress shown with care,
Failures now laid bare,
Debugging conquers fears.
Footnotes
-
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. ↩
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.
Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
lib/cli/ui/Progress.tsx:39
- [nitpick] The arrow function parameter 'title' shadows the outer 'title' prop. Consider renaming it (for example, to 'item') to enhance code clarity.
{(title) => (
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
The pull request introduces a new fail state to the progress indicator, enhancing the user experience by providing visual feedback when build or installation processes encounter errors. The changes are well-structured and improve the clarity of error handling.
Merge Readiness
The code changes are well-implemented and enhance the user experience by providing clear feedback on failures. I am unable to directly approve the pull request, and recommend that others review and approve this code before merging. The changes look good and I recommend merging this pull request.
| await _buildWorkflow(workflowPath); | ||
| await done(getBuildTargetPath(workflowPath)); | ||
| } catch (error) { | ||
| await fail(workflowPath); |
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.
|
|
||
| await done(`${parsedAction.fullName}@${tagName}`); | ||
| } catch (error) { | ||
| await fail(`${parsedAction.fullName}@${parsedAction.version}`); |
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.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #64 +/- ##
=======================================
Coverage 98.10% 98.10%
=======================================
Files 15 15
Lines 581 581
=======================================
Hits 570 570
Misses 11 11 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
No description provided.