Add public announcement tracking git action.

[anjai94]

Adds a scheduled GitHub Action that watches the Projects v2 board and, for each item in the "Batched for Public Announcement" status, automatically applies the relevant PublicPR/Pending from <team> label once the item has been in that status for 30 days — but only for teams whose Patch/<team> Completed label is present.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

📝 Walkthrough

Summary

• Added a daily, manually triggerable GitHub Actions workflow to monitor the Projects v2 board.
• Tracks items in “Batched for Public Announcement” for 30 days.
• Applies the appropriate PublicPR/Pending from <team> labels when required completion labels are present.

Walkthrough

Adds a scheduled and manually triggered GitHub Actions workflow that queries Project v2 items in the “Batched for Public Announcement” status. It marks newly found Issues or PRs, tracks the marker’s earliest timeline event, waits 30 days, and then applies configured target labels when all required source labels are present. Project items are retrieved through paginated GraphQL queries, while labels and timeline events are handled through REST API calls.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is too brief and omits most required template sections, including Purpose, Goals, Approach, tests, and security checks.	Fill in the repository template sections, especially Purpose, Goals, Approach, User stories, Release note, Documentation, Automation tests, and Security checks.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly reflects the main change: adding a scheduled GitHub Action for public announcement tracking.
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.

✨ 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

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

[coderabbitai]

Actionable comments posted: 1

🤖 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/workflows/public-announcement-label.yml:
- Around line 101-103: Update the batching logic at
.github/workflows/public-announcement-label.yml lines 101-103 to retain
processable non-Batched items so the workflow can remove MARKER_LABEL when they
leave the configured status; update the marker-event selection at lines 134-137
to use the most recent marker-label event as the active clock start, ensuring
re-entry begins a fresh tracking interval.

🪄 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: 05ba3748-35d0-49c9-8333-db83ad8cec8a

📥 Commits

Reviewing files that changed from the base of the PR and between 15ce18d and 8979fbe.

📒 Files selected for processing (1)

• .github/workflows/public-announcement-label.yml