We are using gihub to manage our CI/CD pipeline and I noticed that on a PR, every update I run to align the PR with target branch, I trigger the whole unit testing flow, since the head of the branch has changed, I want to explore if this is not a redundant action that can be excluded, if at all.
The testing flow triggers on every push into a published branch, which means that anything that was merged has passed all the tests. This essentially means that any update I run on my branch would include all those PRs that passed the full test flow, so my question is, why would I need to run a full test flow on every update to my branch?
Think about the situation where you have a large team and right before release everyone is putting their PRs in, moreover, after every PR gets merged, my PR would need a new update, which means another test run, github doesn't have "merge after tests complete successfully", so that means that I'm in a race to merge quickly before the next PR merges in, and if I don't > update > test run, would be happy to get your feedback on this.
Thx, Bud