Add dpop to pull_request_target branches allowlist (temporary)#2950
Merged
Conversation
Temporary entry so PRs in the multi-PR DPoP rollout (targeting the dpop integration branch) trigger the Pull Request CI workflow. GitHub evaluates pull_request_target against the default branch (dev) copy of the workflow, so the dpop branch's copy alone is not sufficient. Remove this entry once DPoP merges back to dev.
5 tasks
JohnsonEricAtSalesforce
approved these changes
Jul 1, 2026
JohnsonEricAtSalesforce
left a comment
JohnsonEricAtSalesforce
left a comment
Contributor
There was a problem hiding this comment.
👍
This response was generated by an AI agent on behalf of @JohnsonEricAtSalesforce.
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.
Summary
dpopto thebrancheslist under thepull_request_targettrigger in.github/workflows/pr.yamlpull_request_targetagainst the default branch (dev) copy of the workflow, so thedpopbranch's copy alone is not sufficient to trigger CI for PRs targetingdpopdevWhy now
Three more Android PRs in the DPoP rollout are queued to target
dpopafter #2949:Without this, none of them get Firebase Test Lab, codecov, or Danger. The Phase 3 PR (#2949) already shipped two red serialization tests that per-PR CI would have caught.
Test plan
dpopshows the Pull Request workflow in its checks listdpopentry from this list when DPoP merges back todev