Use two-way merge for PR run
When PR is open only last changeset is retrieved by spacelift. In case the target branch of PR has changed, these changes are not reflected in PR run.
Results of the plan are not the same as results of the plan when the PR is merged.
- Workaround
Log in to comment and vote
Comments1
Aleksandra Cieslak
Nov 13
Hi, thanks for raising this, and sorry for the slow response. I’m a Product Manager at Spacelift and I’d love to understand your setup and how this affects your team.
Would you be open to a short 20–30 minute call? You can pick a time that works for you here: https://calendar.app.google/prDB7URuvYt221cc7
If a call doesn’t suit you, no problem. Just let me know in the comments which VCS provider you use and whether the issue is that the PR plan ignores base branch changes entirely, or that the run isn’t re-triggered when the base branch moves. It would be great if you could provide me an example for better understanding.