Skip to content

💄 Add Gitmoji's to types #15

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.

Sign up for GitHub

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

Merged
rickyheijnen merged 1 commit into from
Aug 7, 2025
Merged

💄 Add Gitmoji's to types #15

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions labels/frontend.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,13 @@
########################################################
# Frontend-specific Type Labels
########################################################
- name: "type: ui"
- name: "type: 💄 ui"
color: "#d472b0"
description: "Bug related to UI/UX or visual presentation"
aliases: ["💄 ui"]
Comment on lines +4 to 7

@coderabbitai coderabbitai Bot Aug 7, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Add legacy alias to avoid breaking existing filters & automation

Replacing the old plain-text label ("type: ui") with an emoji-prefixed one breaks every existing reference (issue templates, saved filters, scripts, CI checks) that still expects "ui". Keep the new name, but include the legacy alias so both forms resolve.

-  aliases: ["💄 ui"]
+  aliases: ["ui", "💄 ui"]

Ensure there are no workflows or queries elsewhere in the repo that rely on the plain "type: ui" label before merging.

🏁 Script executed:

#!/bin/bash
# Search for references to the plain label "type: ui" across the repository
echo "Looking for exact matches of \"type: ui\""
rg -n '"type: ui"' || true

echo "Looking for unquoted occurrences of type: ui"
rg -n 'type:\s*ui' --no-heading || true

Length of output: 256

Add a legacy ui alias for future compatibility

We didn’t find any references to the plain "type: ui" label in workflows, issue templates, or scripts—so there’s no immediate breakage. Still, including the legacy alias ensures any external filters or automations that expect ui will continue to work.

• In labels/frontend.yml, change:

-  aliases: ["💄 ui"]
+  aliases: ["ui", "💄 ui"]
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: "type: 💄 ui"
color: "#d472b0"
description: "Bug related to UI/UX or visual presentation"
aliases: ["💄 ui"]
- name: "type: 💄 ui"
color: "#d472b0"
description: "Bug related to UI/UX or visual presentation"
aliases: ["ui", "💄 ui"]
🤖 Prompt for AI Agents 
In labels/frontend.yml around lines 4 to 7, add the legacy alias "ui" to the
aliases list for the "type: 💄 ui" label. This means updating the aliases array
to include both "💄 ui" and "ui" to maintain compatibility with any external
filters or automations that might expect the plain "ui" alias.


- name: "type: ux"
- name: "type: 🚸 ux"
color: "#e3b140"
description: "Fixes for responsive design or layout issues"
aliases: ["🚸 ux"]

Loading