James Gilchrist
10/01/2025, 3:31 PMon:
pull_request:
branches:
- develop
...
- name: 🚀 Create preview
uses: expo/expo-github-action/preview@v8
with:
command: eas update --auto --non-interactive --branch ${{ github.event.pull_request.head.ref }} --message "${{ env.COMMIT_MSG }} --environment development"
This is a required action for target branch: develop
When I have my stack, only my bottom branch is mergeable. The rest say "Waiting on CI". I do have the Graphite APP on the Bypass List for Always Allow. But I cannot get this to show me "Merge N".
What's the right way to configure this?
• remove the required check on the develop branch?
• make the github action run on all prs, not just targeting develop?
I would also like to avoid some redundant and repeated runs of eas update. When I click merge on the bottom of the stack, it sends it to the merge queue, which then opens a new temporary PR targeting develop, which also runs the eas update before it merges despite it having already run to mark the bottom branch as "Ready to merge".
Thanks in advance for any feedback or suggestions.Pylon
10/01/2025, 3:31 PMPylon
10/01/2025, 5:41 PMWhen I have my stack, only my bottom branch is mergeable. The rest say "Waiting on CI". I do have the Graphite APP on the Bypass List for Always Allow. But I cannot get this to show me "Merge N".
I think the issue here may be that your current trigger is looking for pull requests pointing to the
develop [trunk] which, in the case of a stacked PR wont be true until the ancestor branch is merged and children get restacked. You'd need to revise the trigger here when using stacked branches.
I would also like to avoid some redundant and repeated runs of. When I click merge on the bottom of the stack, it sends it to the merge queue, which then opens a new temporary PR targeting develop, which also runs theeas updatebefore it merges despite it having already run to mark the bottom branch as "Ready to merge".eas update
This is expected behavior today and can seem unintuitive but for merge queue use cases is frequently necessary. As your merge queue has the CI settings option enabled, graphite will always create a draft PR, but you can customize your CI based on the predictable branch and PR name prefix pattern - some reading on that here.