You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Learning:** Adding color-coded indicators (Green/Red) and emojis (💰, 📉) in CLI tools significantly reduces cognitive load when parsing financial data streams. It transforms a wall of text into a scannable narrative.
3
-
**Action:** For data-heavy CLI applications, always implement a semantic color system and visual anchors (icons/emojis) for key events.
4
-
5
-
## 2024-05-23 - Accessibility and Control in CLI Tools
6
-
**Learning:** While color and emojis improve scannability, they can be distracting or inaccessible (e.g., for color-blind users or automated parsing). Providing `--no-color` and `--quiet` flags is essential for accessibility and flexibility.
7
-
**Action:** Always include flags to disable visual enhancements and suppress verbose output in CLI tools to respect user preferences and support automation.
1
+
## 2024-05-23 - CLI UX Enhancement
2
+
**Learning:** Even in CLI apps, visual distinction (colors, emojis) significantly reduces cognitive load when scanning logs.
3
+
**Action:** Use ANSI colors and consistent emojis for key events (success/failure) in future CLI tools.
# required to fetch internal or private CodeQL packs
36
+
packages: read
37
+
38
+
# only required for workflows in private repositories
39
+
actions: read
40
+
contents: read
41
+
42
+
strategy:
43
+
fail-fast: false
44
+
matrix:
45
+
include:
46
+
- language: actions
47
+
build-mode: none
48
+
- language: python
49
+
build-mode: none
50
+
# CodeQL supports the following values keywords for 'language': 'actions', 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'rust', 'swift'
51
+
# Use `c-cpp` to analyze code written in C, C++ or both
52
+
# Use 'java-kotlin' to analyze code written in Java, Kotlin or both
53
+
# Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
54
+
# To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
55
+
# see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
56
+
# If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
57
+
# your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
58
+
steps:
59
+
- name: Checkout repository
60
+
uses: actions/checkout@v4
61
+
62
+
# Add any setup steps before running the `github/codeql-action/init` action.
63
+
# This includes steps like installing compilers or runtimes (`actions/setup-node`
64
+
# or others). This is typically only required for manual builds.
65
+
# - name: Setup runtime (example)
66
+
# uses: actions/setup-example@v1
67
+
68
+
# Initializes the CodeQL tools for scanning.
69
+
- name: Initialize CodeQL
70
+
uses: github/codeql-action/init@v4
71
+
with:
72
+
languages: ${{ matrix.language }}
73
+
build-mode: ${{ matrix.build-mode }}
74
+
# If you wish to specify custom queries, you can do so here or in a config file.
75
+
# By default, queries listed here will override any specified in a config file.
76
+
# Prefix the list here with "+" to use these queries and those in the config file.
77
+
78
+
# For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
79
+
# queries: security-extended,security-and-quality
80
+
81
+
# If the analyze step fails for one of the languages you are analyzing with
82
+
# "We were unable to automatically build your code", modify the matrix above
83
+
# to set the build mode to "manual" for that language. Then modify this step
84
+
# to build your code.
85
+
# ℹ️ Command-line programs to run using the OS shell.
86
+
# 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
87
+
- name: Run manual build steps
88
+
if: matrix.build-mode == 'manual'
89
+
shell: bash
90
+
run: |
91
+
echo 'If you are using a "manual" build mode for one or more of the' \
92
+
'languages you are analyzing, replace this with the commands to build' \
0 commit comments