🎨 Palette: Add emojis to CLI messages for better DX#152
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
There was a problem hiding this comment.
Pull request overview
Adds emoji “visual cues” to AppGuardrail’s CLI output to make key states (info/success/next steps) easier to scan in terminal logs.
Changes:
- Updated several CLI print messages in
scanner/cli/appguardrail.pyto include emojis (skip, created/updated, workflow description, hook description, CodeGraph mode). - Minor refactors to formatting (multi-line
RuntimeErrorraise; one-linepath = ...assignment). - Added a new entry to
.Jules/palette.mddocumenting the emoji-output learning/action.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| scanner/cli/appguardrail.py | Adds emojis to user-facing CLI output strings and makes small formatting-only refactors. |
| .Jules/palette.md | Documents the “emoji palette” learning/action for future automated/style consistency. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| **Learning:** Adding subtle emojis to informative CLI output headers (like "Created/updated files" and "Next steps") provides clearer visual cues for developers scanning long CLI output. | ||
| **Action:** Always include relevant emojis in summary output text to make success and informational messages more visually distinguishable from routine command logs. | ||
|
|
||
| ## 2024-07-01 - Add emojis to CLI messages for better DX |
There was a problem hiding this comment.
Pull request overview
OpenCode reviewed the current-head evidence but found unresolved reviewer or review-agent threads before approval.
Findings
1. HIGH .github/workflows/opencode-review.yml:1 - Unresolved reviewer thread blocks automated approval
- Problem: OpenCode reached an APPROVE control result, but the approval step found unresolved, non-outdated human or review-agent thread evidence on the current pull request.
- Root cause: Reviewer and review-agent feedback can arrive after bounded model evidence is prepared, so the approval step must re-query GitHub immediately before publishing an approval.
- Fix: Address or resolve the listed reviewer thread(s), then re-run OpenCode on the current head.
- Regression test: Keep the approval gate querying reviewThreads(first: 100) after model output and before create_pull_review APPROVE, including bot review agents other than OpenCode itself.
Review thread evidence
Latest unresolved reviewer thread evidence
.Jules/palette.md line 9
-
Latest reviewer comment: @copilot-pull-request-reviewer at 2026-07-01T14:17:37Z
-
Comment URL: #152 (comment)
-
Comment excerpt: The new palette entry date (2024-07-01) is out of sequence with the surrounding 2026 entries and doesn’t match the PR’s timeframe, which makes the palette history misleading.
-
Result: REQUEST_CHANGES
-
Reason: unresolved reviewer or review-agent thread(s) were present before approval.
-
Head SHA:
47b4fad55b762994a96b015061e79e9a8325de18 -
Workflow run: 28524149414
-
Workflow attempt: 1
Changed-File Evidence Map
flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (2 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (2 files)"]
R1 --> V1["required checks"]
OpenCode Review Overview
Pull request overviewOpenCode reviewed the current-head evidence but found unresolved reviewer or review-agent threads before approval. Findings1. HIGH .github/workflows/opencode-review.yml:1 - Unresolved reviewer thread blocks automated approval
Review thread evidenceLatest unresolved reviewer thread evidence
|
💡 What: Added emojis to informational headers and output messages across various CLI commands in
scanner/cli/appguardrail.py.🎯 Why: Emojis serve as helpful visual cues that make important states (like success, information, and next steps) stand out against routine command logs, significantly improving the Developer Experience (DX) when reading CLI output.
📸 Before/After: Visual change in terminal output making it easier to scan and understand the results of CLI operations.
♿ Accessibility: Improves visual structure and readability for developers.
PR created automatically by Jules for task 1180831922571756745 started by @seonghobae