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
I have a question about the expected behavior of gh-stack.
We have a GitHub Actions workflow that relies on the PR base branch. While investigating a workflow failure on a stacked PR, we noticed two behaviors that we didn’t expect.
First, a workflow configured as:
on:
pull_request:
types: [opened, synchronize, reopened]branches:
- master
was triggered for a stacked PR in the preview stage. Is this the expected behavior?
Additionally, our workflow failed because these two values were different:
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.
Uh oh!
There was an error while loading. Please reload this page.
Hi team,
I have a question about the expected behavior of gh-stack.
We have a GitHub Actions workflow that relies on the PR base branch. While investigating a workflow failure on a stacked PR, we noticed two behaviors that we didn’t expect.
First, a workflow configured as:
was triggered for a stacked PR in the preview stage. Is this the expected behavior?
Additionally, our workflow failed because these two values were different:
We expected github.event.pull_request.base.ref and github.base_ref to refer to the same base branch, but they appear to differ for stacked PRs.
Is this the intended behavior? If so, which value should GitHub Actions workflows rely on?
Thanks!
All reactions