chore: add PF Team label workflow

[nicolethoen]

Made-with: Cursor

Summary by CodeRabbit

• Chores
  • Added GitHub Actions workflow for automated issue labeling. Issues will now be automatically categorized when opened.

[coderabbitai]

Warning

Rate limit exceeded

@nicolethoen has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 48 minutes and 39 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d6a5fa16-25ef-449d-8b58-dc702640ff0b

📥 Commits

Reviewing files that changed from the base of the PR and between 6c4461f and a8abd48.

📒 Files selected for processing (1)

• .github/workflows/label-pf-team-issues.yml

Walkthrough

A new GitHub Actions workflow is added to automatically label newly opened issues by invoking a reusable workflow from the PatternFly repository's main branch, forwarding secrets as needed.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/label-pf-team-issues.yml	New workflow that triggers on issue opened events and calls a reusable workflow (patternfly/.github/.github/workflows/add-pf-team-label-workflow.yml) with inherited secrets.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 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 that labels PF Team issues.
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.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

_{Review rate limit: 0/1 reviews remaining, refill in 48 minutes and 39 seconds.}

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.github/workflows/label-pf-team-issues.yml (1)

4-6: ⚡ Quick win

Consider also labeling reopened issues (optional).

Right now the workflow runs only for issues.opened. If your desired behavior is “label newly opened or re-opened issues,” you may want to include reopened as well.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/workflows/label-pf-team-issues.yml around lines 4 - 6, The workflow
currently triggers only on the issues.types value "opened"; to also run for
re-opened issues, add "reopened" to the issues.types array so it contains both
"opened" and "reopened" (e.g., change the types list under the issues trigger to
include - opened and - reopened).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/label-pf-team-issues.yml:
- Around line 1-7: The workflow "Label PF Team issues" is missing explicit
permissions so the GITHUB_TOKEN may lack issues: write and label application can
fail; add a top-level permissions section to this workflow (under the "name:
Label PF Team issues" block) specifying permissions: issues: write so the caller
has explicit write access for labeling, ensuring the reusable labeling workflow
can run reliably.

---

Nitpick comments:
In @.github/workflows/label-pf-team-issues.yml:
- Around line 4-6: The workflow currently triggers only on the issues.types
value "opened"; to also run for re-opened issues, add "reopened" to the
issues.types array so it contains both "opened" and "reopened" (e.g., change the
types list under the issues trigger to include - opened and - reopened).

🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9d1c8f1c-d6aa-4d87-acf6-a9f939c648d4

📥 Commits

Reviewing files that changed from the base of the PR and between 2762694 and 6c4461f.

📒 Files selected for processing (1)

• .github/workflows/label-pf-team-issues.yml