Skip to content

Conversation

@capcom6
Copy link
Member

@capcom6 capcom6 commented Nov 27, 2025

Summary by CodeRabbit

  • Chores
    • Updated internal GitHub Actions workflow automation for pull request management.

Note: This release contains internal infrastructure updates with no direct user-facing changes.

✏️ Tip: You can customize this high-level summary in your review settings.

@cloudflare-workers-and-pages
Copy link

Deploying docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 72fefd9
Status: ✅  Deploy successful!
Preview URL: https://00f842cd.docs-7wm.pages.dev
Branch Preview URL: https://actions-remove-pr-labels.docs-7wm.pages.dev

View logs

@coderabbitai
Copy link

coderabbitai bot commented Nov 27, 2025

Walkthrough

A new GitHub Actions workflow file is added that automatically removes the "ready" and "deployed" labels from pull requests when they are opened or updated, using the gh pr edit command.

Changes

Cohort / File(s) Summary
GitHub Actions Workflow
\.github/workflows/pr-labels\.yml
New workflow triggered on pull_request_target events (opened, synchronize) that removes labels "ready" and "deployed" from PRs using the GitHub CLI.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Straightforward workflow addition with standard GitHub Actions syntax
  • Single file with clear, declarative configuration
  • May benefit from verifying the trigger conditions and label names are correct for project workflow needs

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title contains a typo ('clenup' instead of 'cleanup') and is somewhat vague about which labels are being cleaned up and when, though it does convey the general purpose of the change. Correct the typo and consider clarifying the title, e.g., 'Remove PR labels on new push' or similar, to be more explicit about what the workflow does.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch actions/remove-pr-labels

📜 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 5d331e5 and 72fefd9.

📒 Files selected for processing (1)
  • .github/workflows/pr-labels.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Cloudflare Pages
🔇 Additional comments (2)
.github/workflows/pr-labels.yml (2)

1-16: Workflow structure and permissions look sound.

The workflow is appropriately scoped with pull_request_target (correct for metadata operations requiring secrets), minimal permissions (pull-requests: write), and clear trigger conditions (opened and synchronize). Once the label removal syntax is verified, this should work reliably.


14-14: The gh pr edit --remove-label syntax is correct as written.

The GitHub CLI documentation explicitly supports comma-separated labels in a single --remove-label flag. The command --remove-label "ready,deployed" follows the documented pattern and will correctly remove both labels.


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.

@capcom6 capcom6 merged commit dbc2def into master Nov 27, 2025
2 checks passed
@capcom6 capcom6 deleted the actions/remove-pr-labels branch November 27, 2025 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants