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
Says I have a workflow that supports both single PR and stack PR. I have dedicated jobs for each type.
However, the bottom PR of the stack always have github.event.pull_request.stack to null when it's first created, hence, it echoes "Single PR"
Subsequent pushes to the bottom PR trigger the workflow again but now, it recognizes the stack therefor it echoes "Stacked PR".
Is this intended?
IMO, the pull_request.stack should have returned NOT null for the bottom PR when it's first created.
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
Uh oh!
There was an error while loading. Please reload this page.
Says I have a workflow that supports both single PR and stack PR. I have dedicated jobs for each type.
However, the bottom PR of the stack always have github.event.pull_request.stack to null when it's first created, hence, it echoes "Single PR"
Subsequent pushes to the bottom PR trigger the workflow again but now, it recognizes the stack therefor it echoes "Stacked PR".
Is this intended?
IMO, the pull_request.stack should have returned NOT null for the bottom PR when it's first created.
see https://docs.github.com/en/pull-requests/how-tos/merge-and-close-pull-requests/optimizing-ci-for-stacked-pull-requests
All reactions