You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This action just got triggered by pushing subsequent commit to already opened PR, this commit contains some js file alone which is clearly not on the list. Also I noticed that the action got triggered on main repo inside pull request, but my fork did not triggered it, just as expected.
BugSomething isn't working correctlyActionsBuild, test, and automate your deployment pipeline with world-class CI/CD
2 participants
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Bug
Body
My action uses
pull_request:synchronize
event with specific paths to trigger, but it looks like thesynchronize
event ignores all these rules.My action trigger rules:
This action just got triggered by pushing subsequent commit to already opened PR, this commit contains some
js
file alone which is clearly not on the list. Also I noticed that the action got triggered on main repo inside pull request, but my fork did not triggered it, just as expected.Beta Was this translation helpful? Give feedback.
All reactions