Repository navigation
redo first_interaction trigger - #3606
Merged
Merged
Conversation
copybara-service
Bot
force-pushed
the
test_1014105455
branch
2 times, most recently
from
November 9, 2026 19:07
1a4d6ee to
b25c1b9
Compare
I had to remove pull_request_target from the first_interaction workflow, so after doing a little research I found that the "right" way to do this is to separate it into two workflows: first triggers on PR open and records the PR number in an artifact. Second triggers after the first finishes, reads the PR number, and has the relevant permissions to comment on the PR. PiperOrigin-RevId: 1017500242
copybara-service
Bot
force-pushed
the
test_1014105455
branch
from
November 9, 2026 19:27
b25c1b9 to
92f2e0e
Compare
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
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.
redo first_interaction trigger
I had to remove pull_request_target from the first_interaction workflow, so after doing a little research I found that the "right" way to do this is to separate it into two workflows: first triggers on PR open and records the PR number in an artifact. Second triggers after the first finishes, reads the PR number, and has the relevant permissions to comment on the PR.