Skip to content

💄 Add Gitmoji's to type labels to backend #16

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 type labels to backend #16

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
7 changes: 4 additions & 3 deletions labels/backend.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,17 +1,18 @@
########################################################
# Backend-specific Type Labels
########################################################
- name: "type: business-logic"
- name: "type: 👔 business-logic"
color: "#3585BD"
description: "Business logic implementation or changes"
aliases: []
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.

⚠️ Potential issue

Missing alias for the previous label name breaks existing automation

Renaming the label from
"type: business-logic" → "type: 👔 business-logic"
without keeping the old name as an alias will break any workflows, issue templates, or 3rd-party tools that still reference the original label string.

Add the legacy name as an alias:

-  aliases: []
+  aliases: ["type: business-logic"]
🤖 Prompt for AI Agents 
In labels/backend.yml around lines 4 to 7, the label name was changed from
"type: business-logic" to "type: 👔 business-logic" but the old name was not
kept as an alias. To fix this, add "type: business-logic" to the aliases array
for this label to maintain compatibility with existing workflows and tools that
reference the old label name.


- name: "type: database"
- name: "type: 🗃️ database"
color: "#2E8B57"
description: "Database schema, queries, or migrations"
aliases: []
Comment on lines +9 to 12

@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.

⚠️ Potential issue

Same compatibility gap for the database label

The original "type: database" label has been removed without an alias, causing the same backward-compatibility problem.

-  aliases: []
+  aliases: ["type: database"]
📝 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: 🗃️ database"
color: "#2E8B57"
description: "Database schema, queries, or migrations"
aliases: []
- name: "type: 🗃️ database"
color: "#2E8B57"
description: "Database schema, queries, or migrations"
- aliases: []
+ aliases: ["type: database"]
🤖 Prompt for AI Agents 
In labels/backend.yml around lines 9 to 12, the original label "type: database"
was removed without adding it as an alias to the new "type: 🗃️ database" label.
To fix this backward-compatibility issue, add "type: database" as an alias in
the aliases list of the new label so that references to the old label still work
correctly.


- name: "type: endpoint"
- name: "type: 🔗 endpoint"
color: "#8B572E"
description: "Endpoint implementation or changes"
aliases: ["🔗 endpoint"]

Comment on lines +14 to +18

@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.

⚠️ Potential issue

Endpoint label keeps only the new name in the aliases array

The alias list now contains only the emoji-prefixed variant, so clients that still emit "endpoint" (without the emoji) will fail. Preserve both:

-  aliases: ["🔗 endpoint"]
+  aliases: ["endpoint", "🔗 endpoint"]
📝 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: 🔗 endpoint"
color: "#8B572E"
description: "Endpoint implementation or changes"
aliases: ["🔗 endpoint"]
- name: "type: 🔗 endpoint"
color: "#8B572E"
description: "Endpoint implementation or changes"
aliases: ["endpoint", "🔗 endpoint"]
🤖 Prompt for AI Agents 
In labels/backend.yml around lines 14 to 18, the aliases array for the "type: 🔗
endpoint" label currently only includes the emoji-prefixed alias "🔗 endpoint".
To fix this, add back the original alias "endpoint" alongside the emoji-prefixed
one in the aliases array to ensure compatibility with clients that emit either
variant.

Loading