ci: add GHA to add PRs to project board when marked ready for review#5026
Open
MikeGoldsmith wants to merge 2 commits intoopen-telemetry:mainfrom
Open
ci: add GHA to add PRs to project board when marked ready for review#5026MikeGoldsmith wants to merge 2 commits intoopen-telemetry:mainfrom
MikeGoldsmith wants to merge 2 commits intoopen-telemetry:mainfrom
Conversation
The board's built-in auto-add workflow only fires on PR open/reopen, not when a draft is converted to ready for review. This GHA covers that gap by triggering on opened, reopened, and ready_for_review, skipping drafts. Assisted-by: Claude Sonnet 4.6
1 task
Member
Author
|
Please add the skip-changelog label. |
xrmx
approved these changes
Mar 31, 2026
Contributor
|
This is failing with |
…kflow pull_request trigger cannot access secrets for fork PRs (Secret source: None). pull_request_target runs in base repo context and can access secrets. Use otelbot app token (same pattern as backport.yml) instead of a PAT. No checkout step — intentional, see open-telemetry#4955. Assisted-by: Claude Sonnet 4.6
MikeGoldsmith
moved this from Easy to review / merge / close
to Approved PRs
in Python PR digest
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The Python PR digest board uses a built-in GitHub project workflow to auto-add PRs. However, that workflow only fires on PR `opened` and `reopened` events — it does not fire when a draft PR is converted to ready for review.
This means any PR opened as a draft and later marked ready for review is silently skipped and never added to the board.
Examples: The following resource detector PRs were all opened as drafts and missed the board as a result:
This GHA covers the gap by triggering on `opened`, `reopened`, and `ready_for_review`, while skipping drafts. Since it uses `actions/add-to-project` (which is idempotent), PRs opened as non-drafts are safe — they'll just be a no-op on the second trigger.
Security: `pull_request_target` trigger
This workflow uses `pull_request_target` rather than `pull_request`. This is intentional: `pull_request` does not have access to repository secrets for fork PRs (`Secret source: None`), so the otelbot token would never resolve. `pull_request_target` runs in the base repo context and can access secrets.
The workflow contains no `actions/checkout` step — it never executes any code from the fork, only uses the PR node ID to make a single GitHub API call. See #4955 for the full security discussion.
Prerequisites for org admins
Before this workflow will function after merge, an org admin must grant otelbot the Projects permission: