Feat/automatic pr labellng

[SaranHiruthikM]

Description

This PR introduces automatic Pull Request labeling using GitHub Actions. As contributor activity increases, this automation will help improve PR categorization, simplify repository triaging, and significantly reduce the manual workload for maintainers.

Changes Introduced

• Created .github/labeler.yml to define the label mapping rules based on file paths.
• Created .github/workflows/label.yml to set up the GitHub Action workflow that runs on PR events.

Expected Behavior

The workflow detects modified files in a Pull Request and automatically assigns the following labels:

• Frontend (for any changes in the frontend/** directory)
• backend (for any changes in the server/** directory)
• docs (for any changes to **/*.md files)

Summary by CodeRabbit

• Chores
  • Configured automatic labeling for pull requests and issues based on changed files.

[github-actions]

🚀 PR Received Successfully

Hello @SaranHiruthikM,

Thank you for taking the initiative to contribute to this project.

Please ensure that your PR follows all project guidelines properly before requesting review.

⚠️ Important Instructions

• Maintain proper code quality and structure
• Do not make unnecessary changes/files
• Ensure responsiveness across devices
• Follow existing project conventions strictly
• Attach screenshots/videos for UI-related changes
• Resolve merge conflicts before requesting review
• Avoid AI-generated low quality PRs or copied implementations

📌 Mandatory for GSSoC'26 Participants

Joining the community group and announcement channel is compulsory for all contributors participating through GSSoC'26.

• Telegram Group: https://t.me/c/3991077814/1
• Telegram Channel: https://t.me/+g4esQdo-DyNlZWE1

Failure to follow contribution guidelines may lead to PR rejection.

We appreciate your effort and wish you a great open-source journey ahead. ✨

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds GitHub Actions automation to automatically label pull requests based on file path patterns. A new labeler configuration file maps frontend directory changes to a Frontend label, server directory changes to a backend label, and markdown files to a documentation label. A corresponding workflow triggers the labeler action on PR open, synchronize, and reopen events.

Changes

Automatic PR Labeling Setup

Layer / File(s)	Summary
Labeler configuration and workflow .github/labeler.yml, .github/workflows/label.yml	Path-based label rules defined for frontend/** (Frontend), server/** (backend), and **/*.md (documentation) files, with GitHub Actions workflow triggering actions/labeler@v4 on PR lifecycle events using repository token and label synchronization enabled.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related issues

• [Feature] Setup Automatic Pull Request Labeling Based on Changed Files #64: Directly implements the automatic PR labeling feature using the same configuration and workflow files.

Poem

🐰 Labels hop and organize with care,
Frontend and backend sorted fair,
Docs marked gentle, docs marked bright,
PRs now classified just right!
Automation's dance, so light!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Feat/automatic pr labellng' is partially related to the changeset but contains a spelling error ('labellng' instead of 'labeling') and uses a branch-naming convention rather than a clear PR title format.	Improve the title to be more professional and clear: 'Add automatic PR labeling workflow' or similar, following conventional commit format without the 'Feat/' prefix.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

Adds GitHub Actions-based automation to label pull requests based on which parts of the repository were modified, to reduce manual triage effort.

Changes:

• Added a PR labeling workflow using actions/labeler.
• Added a label mapping configuration file to map paths (frontend/server/markdown) to labels.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/label.yml	Introduces a workflow that runs the labeler on pull_request_target events and applies labels.
.github/labeler.yml	Defines the label-to-path rules used by the labeler action.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/labeler.yml:
- Around line 2-11: The label config uses inconsistent names: "Frontend"
(capitalized), "backend" and "documentation", which also don't match the PR
text; update the label keys so they are consistent, lowercase, and match the PR
description by renaming "Frontend" to "frontend" and "documentation" to "docs"
while keeping "backend" unchanged; ensure the pattern entries under each label
(e.g., "frontend/**", "server/**", "**/*.md") remain the same and test the
labeler to confirm PRs get the frontend, backend, and docs labels.

In @.github/workflows/label.yml:
- Line 13: Update the GitHub Actions labeler step to use the current stable
release by replacing the reference "actions/labeler@v4" with
"actions/labeler@v6.1.0"; locate the workflow step that contains the uses:
action string (the labeler step) and update the version tag to v6.1.0 to ensure
you get the latest fixes and features.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b5f369aa-fbeb-4518-97d7-483984b37ab7

📥 Commits

Reviewing files that changed from the base of the PR and between 4879f17 and 66f1eea.

📒 Files selected for processing (2)

• .github/labeler.yml
• .github/workflows/label.yml

[SaranHiruthikM]

Solves #64

cc: @kunalverma2512