Good afternoon :slightly_smiling_face: I would ha...
# how-do-i
k
Good afternoon šŸ™‚ I would have a small question about the CI optimization with github actions. If we set the settings to: • Run on bottom PR • Run on topmost PR Let's say that an engineer open a stack with 4 PRs, it'll run on PR1 and PR4, do they still have the option to merge only the 3 first PRs ? In the worst case, the fourth PR is fixing a bug on PR3 so I was curious what is behavior there before checking it for my org šŸ™‚ Same if they remove the 4th PR from the stack, can they merge a stack where the topmost was not checked anymore ? Thank you a lot šŸ™‚
p
(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about: - Screenshots / debug logs / list of commands you've tried to run so far - Your workflow - Current state
hey Kenny, I believe the CI Optimization settings only control which PRs in a stack run CI checks so they don't restrict which PRs can be merged. In terms of "removing" the 4th PR from the stack, do you mean closing the PR or deleting the branch locally and submitting? For the latter I'm unsure what the behavior would be but I suspect the 3rd PR would just become the top in the stack.
k
Hey Gary šŸ˜„ Yeah that's what I thought, my main concern was that it'd allow then to merge a PR where the CI never ran, but that's expected since it's an optimization, I'll discuss it with my team Thank you for the explanations šŸ™‚ For removing, I meant closing šŸ™‚