-
-
Notifications
You must be signed in to change notification settings - Fork 0
[email protected] #60
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
- fix utp table rendering in ci builds
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.
Pull request overview
This PR bumps the version to 1.7.2 and prevents UTP (Unity Test Platform) table rendering in CI builds.
Key changes:
- Extracted UTP processing logic into a separate
printUTPfunction for better code organization - Changed UTP telemetry log file extension from
.jsonto.json.logand removed pretty-printing - Modified stdout writing to use direct
process.stdout.write()for regular log lines, avoiding unnecessary table manipulation
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| src/unity-logging.ts | Refactored UTP handling by extracting printUTP function, changed telemetry log format, and modified stdout writing behavior |
| src/cli.ts | Added default value documentation to log-level option |
| package.json | Version bump to 1.7.2 |
| package-lock.json | Version bump to 1.7.2 |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Pull request overview
Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- prevent utp table from rendering in ci builds
Uh oh!
There was an error while loading. Please reload this page.