Skip to content

Add warning emoji ⚠️ #383

@nirs

Description

@nirs

This is a very old emoji supported since Unicode 4.0.
https://www.compart.com/en/unicode/U+26A0

We can use it for stale status, and maybe for warnings in the console, instead of error. We can keep the error status of the conclusion line.

The following info provided by Cursor/Claude Opus 4.5.

Overview

Property Value
Character ⚠️
Unicode U+26A0
Name WARNING SIGN
Added Unicode 4.0 (2003)
Emoji Version 1.0 (2015)
Category Symbols

Platform Support

Browsers

Browser Supported Notes
Chrome ✅ Yes Since ~2010
Firefox ✅ Yes Since ~2010
Safari ✅ Yes Since ~2010
Edge ✅ Yes All versions
Opera ✅ Yes Since ~2010

Operating Systems

OS Supported Since
macOS ✅ Yes 10.7 Lion (2011)
Windows ✅ Yes Windows 8 (2012), better in 10+
Linux ✅ Yes With proper fonts (Noto, Symbola)
iOS ✅ Yes iOS 5 (2011)
Android ✅ Yes Android 4.3 (2013)

Terminals

Terminal Supported Notes
iTerm2 (macOS) ✅ Yes Full color emoji
Terminal.app (macOS) ✅ Yes Full color emoji
Windows Terminal ✅ Yes Full color emoji
GNOME Terminal ✅ Yes Requires emoji font
Konsole (KDE) ✅ Yes Requires emoji font
xterm ⚠️ Limited Depends on font, often monochrome
PuTTY ❌ No Shows placeholder
SSH sessions ⚠️ Varies Depends on client terminal

Terminal requirements:

  • UTF-8 locale (LANG=en_US.UTF-8 or similar)
  • Font with emoji glyphs (Noto Color Emoji, Apple Color Emoji, Segoe UI Emoji)
  • Terminal emulator with emoji rendering support

Code Hosting / Documentation

Platform Supported
GitHub ✅ Yes
GitLab ✅ Yes
Bitbucket ✅ Yes
Notion ✅ Yes
Confluence ✅ Yes
VS Code ✅ Yes
JetBrains IDEs ✅ Yes

Email Clients

Client Supported
Gmail ✅ Yes
Apple Mail ✅ Yes
Outlook ✅ Yes (web/modern), ⚠️ varies (old desktop)
Thunderbird ✅ Yes

Recommendations

Use ⚠️ when:

  • Writing markdown for web viewing (GitHub, docs sites)
  • Creating documentation viewed in modern editors
  • Writing content for browsers
  • CLI tools targeting modern users (DevOps, developers, Kubernetes ecosystem)

Many popular CLI tools use emojis: npm, yarn, pnpm, brew, cargo-based tools.

Consider text alternatives when:

  • Structured output meant for parsing (JSON, YAML, CSV) - but emojis
    shouldn't be in structured data anyway
  • Logs will be viewed in basic text editors
  • Targeting legacy systems (RHEL 6, ancient terminals)
  • Users might SSH from Windows with PuTTY

Note: Progress/status messages for human consumption are fine with emojis.
The parsing concern only applies to structured data output, which should be
separate from human-readable messages anyway.

Optional: Environment detection

Some tools detect terminal capabilities and fall back:

import sys
import os

def warning_prefix():
    # Check if output is a TTY and likely supports emoji
    if sys.stderr.isatty() and os.environ.get("TERM") != "dumb":
        return "⚠️ "
    return "WARNING: "

Text alternatives:

  • WARNING:
  • [WARNING]
  • **Warning:** (for markdown output)

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions