💄 Add Gitmoji to type labels for better recognizability

[LegeBeker]

🔍 Samenvatting

Deze PR voegt Gitmoji's toe aan de types voor een betere visuele herkenbaarheid

📝 Beschrijving

• Gitmoji's toegevoegd aan alle 'type'-labels

[coderabbitai]

Walkthrough

The update modifies the "type" labels in the labels/general.yml, labels/backend.yml, and labels/frontend.yml configuration files by adding relevant emoji prefixes to each label name. Corresponding aliases are expanded to include the original non-emoji label names. No other label properties or categories are changed.

Changes

Cohort / File(s)	Change Summary
General Labels Emoji Prefix Update labels/general.yml	Added emoji icons as prefixes to each "type" label name and expanded aliases to include original names without emojis.
Backend Labels Emoji Prefix Update labels/backend.yml	Added emoji prefixes to backend-specific "type" labels and updated aliases to include original non-emoji names for backward compatibility.
Frontend Labels Emoji Prefix Update labels/frontend.yml	Added emoji prefixes to frontend-specific "type" labels and expanded aliases to include original non-emoji names for backward compatibility.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• 💄 Add Gitmoji's to types #15: Adds emoji prefixes and alias updates to frontend labels; this PR extends those changes to general and backend labels as well.
• ✨ Add general labels to sync between all repositories #1: Introduces the initial label configuration files and sets the foundation for label naming conventions updated here.
• 💄 Add Gitmoji's to type labels to backend #16: Applies emoji prefixing and alias additions across multiple label files including backend, frontend, and general, overlapping with this PR’s scope.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eeabf59 and 57e3440.

📒 Files selected for processing (1)

• labels/general.yml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• labels/general.yml

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch style/add-gitmoji-to-types

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

labels/general.yml (1)

9-13: Alias list contains the new canonical name – redundant entry

"✨ feature" is now the primary name, yet it is still present in aliases:. EndBug/label-sync ignores aliases that equal the canonical name, so this line can be removed to keep the config tidy:

-  aliases: ["🌟 feature", "✨ feature"]
+  aliases: ["🌟 feature"]

(Same pattern may apply to other labels—worth a quick sweep.)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 904a089 and a16f2c0.

📒 Files selected for processing (1)

• labels/general.yml (1 hunks)

🧰 Additional context used

🧠 Learnings (6)

📓 Common learnings

Learnt from: rickyheijnen
PR: brixion/.github#1
File: labels/general.yml:4-6
Timestamp: 2025-07-20T16:37:59.036Z
Learning: The EndBug/label-sync GitHub Action (https://github.com/marketplace/actions/label-sync) specifically supports color values with or without a leading '#' character, unlike most other label sync actions which require hex codes without the '#'. When reviewing label configuration files that use EndBug/label-sync, the '#' prefix can be retained for better VS Code color preview functionality.

📚 Learning: the endbug/label-sync github action (https://github.com/marketplace/actions/label-sync) specifically...

Learnt from: rickyheijnen
PR: brixion/.github#1
File: labels/general.yml:4-6
Timestamp: 2025-07-20T16:37:59.036Z
Learning: The EndBug/label-sync GitHub Action (https://github.com/marketplace/actions/label-sync) specifically supports color values with or without a leading '#' character, unlike most other label sync actions which require hex codes without the '#'. When reviewing label configuration files that use EndBug/label-sync, the '#' prefix can be retained for better VS Code color preview functionality.

Applied to files:

• labels/general.yml

📚 Learning: the label-sync github action accepts color values with or without a leading '#' character. when revi...

Learnt from: rickyheijnen
PR: brixion/.github#1
File: labels/general.yml:4-6
Timestamp: 2025-07-20T16:37:59.036Z
Learning: The label-sync GitHub Action accepts color values with or without a leading '#' character. When reviewing label configuration files for label-sync, the '#' prefix should be retained as it provides color preview functionality in VS Code while remaining valid for the action.

Applied to files:

• labels/general.yml

📚 Learning: the label-sync github action supports color values both with and without a leading '#' character. wh...

Learnt from: rickyheijnen
PR: brixion/.github#1
File: labels/backend.yml:4-17
Timestamp: 2025-07-20T16:37:29.125Z
Learning: The label-sync GitHub Action supports color values both with and without a leading '#' character. When using the '#' prefix, the color value should be quoted in YAML. Many developers prefer keeping the '#' for better VS Code color preview functionality.

Applied to files:

• labels/general.yml

📚 Learning: label-sync github action supports color values both with and without a leading '#' character. users ...

Learnt from: rickyheijnen
PR: brixion/.github#1
File: labels/backend.yml:4-17
Timestamp: 2025-07-20T16:37:29.125Z
Learning: label-sync GitHub Action supports color values both with and without a leading '#' character. Users may prefer to keep the '#' prefix for better VS Code color preview functionality.

Applied to files:

• labels/general.yml

📚 Learning: the label-sync github action accepts color values both with and without a leading '#' character, as ...

Learnt from: rickyheijnen
PR: brixion/.github#1
File: labels/frontend.yml:4-12
Timestamp: 2025-07-20T16:37:26.121Z
Learning: The label-sync GitHub Action accepts color values both with and without a leading '#' character, as documented in their specification.

Applied to files:

• labels/general.yml