Skip to content

Create workflow to auto add labels to issues#10700

Merged
stnguyen90 merged 1 commit intomainfrom
chore-issue-auto-labeler
Oct 24, 2025
Merged

Create workflow to auto add labels to issues#10700
stnguyen90 merged 1 commit intomainfrom
chore-issue-auto-labeler

Conversation

@stnguyen90
Copy link
Copy Markdown
Contributor

@stnguyen90 stnguyen90 commented Oct 24, 2025 •
edited
Loading

What does this PR do?

#10430 was merged before to auto label issues, but #10677 inadvertently deleted the files. This PR cherry picks the previous commit to add the files back

Test Plan

None

Related PRs and Issues

Checklist

  • Have you read the Contributing Guidelines on issues?
  • If the PR includes a change to an API's metadata (desc, label, params, etc.), does it also include updated API specs and example docs?

@stnguyen90 stnguyen90 marked this pull request as ready for review October 24, 2025 18:26
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Oct 24, 2025 •
edited
Loading

📝 Walkthrough

Walkthrough

This PR introduces automated GitHub issue labeling infrastructure by adding two configuration files. A labeler configuration file (.github/labeler.yml) defines label groups mapping Appwrite component areas (auth, realtime, storage, databases, functions, migrations, messaging, relationships, vcs, graphql, assistant, domains, locale, avatars, sites, cli, self-hosted) to keyword patterns using regular expressions. A GitHub Actions workflow (.github/workflows/auto-label-issue.yml) triggers on issue creation and uses the github/issue-labeler action to automatically apply labels based on issue title and content matched against the defined patterns.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

The changes consist of straightforward configuration files with simple keyword-to-label mappings. Review effort involves verifying that regex patterns are accurate, workflow permissions are appropriate, and the labeler configuration correctly captures intended component areas without false positives.

Possibly related PRs

Suggested reviewers

  • eldadfux

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed The PR description is clearly related to the changeset and provides meaningful context about the change. It explains that the PR restores files previously added in PR #10430 that were inadvertently deleted by PR #10677, establishing the motivation for re-adding the auto-labeling workflow files. The description includes relevant references to related PRs and a completed checklist, demonstrating that the contributor followed the project's contribution guidelines.
Title Check ✅ Passed The PR title "chore: create workflow to auto add labels to issues" is clearly related to the changeset, which adds two files: .github/workflows/auto-label-issue.yml (a GitHub Actions workflow) and .github/labeler.yml (a labeler configuration file). The title accurately captures the primary objective—creating an automated workflow to label issues—which is the main driver of this change. While the title doesn't explicitly mention the configuration file, the labeler configuration is supporting infrastructure necessary for the workflow to function, making it a secondary implementation detail. The title is concise, specific, and would clearly communicate to a teammate scanning history that issue auto-labeling automation was added.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore-issue-auto-labeler

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

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

@stnguyen90 stnguyen90 requested a review from EVDOG4LIFE October 24, 2025 18:27
@stnguyen90 stnguyen90 changed the title chore: create workflow to auto add labels to issues Create workflow to auto add labels to issues Oct 24, 2025
@github-actions
Copy link
Copy Markdown

github-actions bot commented Oct 24, 2025

Security Scan Results for PR

Docker Image Scan Results

Package Version Vulnerability Severity
binutils 2.44-r2 CVE-2025-5244 HIGH
binutils 2.44-r2 CVE-2025-5245 HIGH
libxml2 2.13.8-r0 CVE-2025-49794 CRITICAL
libxml2 2.13.8-r0 CVE-2025-49796 CRITICAL
libxml2 2.13.8-r0 CVE-2025-49795 HIGH
libxml2 2.13.8-r0 CVE-2025-6021 HIGH
pcre2 10.43-r1 CVE-2025-58050 CRITICAL
golang.org/x/crypto v0.31.0 CVE-2025-22869 HIGH
golang.org/x/oauth2 v0.24.0 CVE-2025-22868 HIGH
stdlib 1.22.10 CVE-2025-47907 HIGH

Source Code Scan Results

🎉 No vulnerabilities found!

EVDOG4LIFE
EVDOG4LIFE approved these changes Oct 24, 2025
View reviewed changes
Copy link
Copy Markdown
Contributor

@EVDOG4LIFE EVDOG4LIFE left a comment

Choose a reason for hiding this comment

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

lgtm, only minor nit below

@github-actions
Copy link
Copy Markdown

github-actions bot commented Oct 24, 2025

✨ Benchmark results

  • Requests per second: 1,187
  • Requests with 200 status code: 213,774
  • P99 latency: 0.164625213

⚡ Benchmark Comparison

Metric This PR Latest version
RPS 1,187 1,192
200 213,774 214,659
P99 0.164625213 0.173541311

@stnguyen90 stnguyen90 merged commit 6ded8dc into main Oct 24, 2025
41 checks passed
@stnguyen90 stnguyen90 deleted the chore-issue-auto-labeler branch October 24, 2025 21:50
This was referenced Oct 27, 2025
Merged
Merged
@coderabbitai coderabbitai bot mentioned this pull request Nov 3, 2025
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@EVDOG4LIFE EVDOG4LIFE EVDOG4LIFE approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@stnguyen90 @EVDOG4LIFE