chore: Add workflow to auto-label community PRs from forks

[aaronsteers]

Summary

Adds a GitHub Actions workflow that automatically applies the community label to PRs opened from forks. This enables automatic tracking on the Community PRs project board.

The workflow:

• Triggers on pull_request_target events (opened and reopened)
• Only runs for PRs from forks (via if: github.event.pull_request.head.repo.fork == true)
• Uses the actions-ecosystem/action-add-labels marketplace action (v1.1.3, pinned by SHA)
• The action's addLabels API is idempotent—if the label already exists, it succeeds without error

Review & Testing Checklist for Human

• Verify the workflow does NOT checkout or execute any code from the fork (security requirement for pull_request_target)
• Confirm the community label exists in this repository
• Verify the pinned action SHA (bd52874380e3909a1ac983768df6976535ece7f8) matches v1.1.3

Test plan: After merging, open a PR from a fork (or close/reopen an existing fork PR) to verify the label is applied automatically.

Notes

This workflow cannot be tested via CI since it only triggers on actual fork PRs.

Requested by: @aaronsteers (AJ Steers)
Devin session: https://app.devin.ai/sessions/b0784474061f4084a04ce5251ce1e9f2

Important

Auto-merge enabled.

This PR is set to merge automatically when all requirements are met.

Note

Auto-merge may have been disabled. Please check the PR status to confirm.

Summary by CodeRabbit

• Chores
  • Implemented automated labeling for community pull requests to streamline contribution tracking and organization.

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

[devin-ai-integration]

Original prompt from AJ Steers

Received message in Slack channel #community-open-source:

@Devin - Please update our workflows so that new PRs from forks automatically are labeled (in not already) and we'll auto-add by label to a specific project board (projects v2).
Thread URL: https://airbytehq-team.slack.com/archives/C06EVC83UGH/p1765393144180229

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

Testing This CDK Version

You can test this version of the CDK using the following:

# Run the CLI from this branch:
uvx 'git+https://github.com/airbytehq/airbyte-python-cdk.git@devin/1765396828-label-community-prs#egg=airbyte-python-cdk[dev]' --help

# Update a connector to use the CDK from this branch ref:
cd airbyte-integrations/connectors/source-example
poe use-cdk-branch devin/1765396828-label-community-prs

Helpful Resources

• CDK API Reference

PR Slash Commands

Airbyte Maintainers can execute the following slash commands on your PR:

• /autofix - Fixes most formatting and linting issues
• /poetry-lock - Updates poetry.lock file
• /test - Runs connector tests with the updated CDK
• /prerelease - Triggers a prerelease publish with default arguments
• /poe build - Regenerate git-committed build artifacts, such as the pydantic models which are generated from the manifest JSON schema in YAML.
• /poe <command> - Runs any poe command in the CDK environment

📝 Edit this welcome message.

[Copilot]

Pull request overview

This PR adds a GitHub Actions workflow to automatically label PRs from forks with a community label, enabling tracking on the Community PRs project board.

• Introduces a new workflow that triggers on PR open/reopen events from forks
• Uses pull_request_target with restricted permissions to safely handle fork PRs
• Leverages a marketplace action pinned to a specific SHA for stability

---

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

[coderabbitai]

📝 Walkthrough

Walkthrough

A new GitHub Actions workflow was added to label pull requests from forked repositories with the "community" label on opened and reopened events; it checks that the PR head repo is a fork and applies the label idempotently via an action.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/label-community-prs.yml	Added workflow triggered on pull_request_target (opened, reopened). Runs on ubuntu-24.04, gated to run only when the PR head repository is a fork, and applies the community label using actions-ecosystem/action-add-labels with write permissions for issues and pull-requests.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Review focus: confirm the fork detection condition and the action version/commit used for label application — wdyt?

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding a GitHub Actions workflow to automatically label community PRs from forks.
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 devin/1765396828-label-community-prs

---

📜 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 f954fef and a361aba.

📒 Files selected for processing (1)

• .github/workflows/label-community-prs.yml (1 hunks)

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

• .github/workflows/label-community-prs.yml

⏰ 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). (4)

• GitHub Check: Pytest (Fast)
• GitHub Check: SDM Docker Image Build
• GitHub Check: Manifest Server Docker Image Build
• GitHub Check: Analyze (python)

---

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

[github-actions]

PyTest Results (Fast)

3 818 tests  ±0   3 806 ✅ ±0   6m 33s ⏱️ +18s
    1 suites ±0      12 💤 ±0 
    1 files   ±0       0 ❌ ±0 

Results for commit a361aba. ± Comparison against base commit daf7d48.

♻️ This comment has been updated with latest results.