Skip to content

[guidelines] fix obvious guideline violations in 2 file(s) - #3677

Merged
pelikhan merged 1 commit into
mainfrom
guidelines-enforcer-fix-checkpoint-emoji-1790049351-d6f741e959c8b087
Sep 22, 2026
Merged

pelikhan merged 1 commit into
mainfrom
guidelines-enforcer-fix-checkpoint-emoji-1790049351-d6f741e959c8b087

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Files changed

workshop/side-quest-11-09-agent-session-phases.md

  • Checkpoint heading uses raw Unicode emoji instead of GitHub shortcode
    • Before: ## ✅ Checkpoint
    • After: ## :white_check_mark: Checkpoint

workshop/side-quest-12-01-iterate-agent-output.md

  • Checkpoint heading uses raw Unicode emoji instead of GitHub shortcode
    • Before: ## ✅ Checkpoint
    • After: ## :white_check_mark: Checkpoint

Rule violated

Per .github/workflows/guidelines.md ("GitHub emoji shortcodes for icons and visual elements"):

Write checkpoint headings as ## :white_check_mark: Checkpoint so they use the same browser-independent rendering as other icons.

Both files used the raw Unicode ✅ character in prose (outside a code block), which is a mechanical, unambiguous fix — the file uses the same heading elsewhere with the correct shortcode convention used across all other workshop files.

Reviewed 15 files in this round-robin batch (indices 410–424); no other obvious or complex violations were found in the remaining 13 files.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

  • registry.npmjs.org

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "registry.npmjs.org"

See Network Configuration for more information.

Generated by 📋 Guidelines Enforcer · copilot · auto · 87.2 AIC · ⌖ 13.8 AIC · ⊞ 9.1K · ◷

  • expires on Sep 25, 2026, 3:58 AM UTC

- Use ✅ shortcode instead of raw Unicode checkmark in Checkpoint heading

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation guidelines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant