| commit | 814e1b71a02d7c698d6793077e946646ca4c2f64 | |
| author | Julien Cristau <jcristau@mozilla.com> | |
| Fri, 13 Jan 2023 15:47:01 +0000 (13 16:47 +0100) | ||
| committer | Julien Cristau <jcristau@mozilla.com> | |
| Fri, 13 Jan 2023 16:44:30 +0000 (13 17:44 +0100) | ||
| tree | 71a8291793cf4fe15bbc619fff69eaef3c70a327 | treesnapshot (tar.gz zip) |
| parent | 5c4a74de06147089826f558a3e6d629448921749 | commitdiff |
Bug 1810150 - stop scheduling pull-request task graphs when there's already a corresponding push graph
When a PR is opened from a branch in the main repo, we used to create a
task graph for both the push event and the pull-request open or
synchronize event, associated with the same commit, and thus essentially
doing the same work twice.
With this change, we skip the pull-request graph, and rely on the push
graph to run the required checks. This requires corresponding changes
to the mergify config to consider either of complete-pr or complete-push
as good enough to merge a PR.
When a PR is opened from a branch in the main repo, we used to create a
task graph for both the push event and the pull-request open or
synchronize event, associated with the same commit, and thus essentially
doing the same work twice.
With this change, we skip the pull-request graph, and rely on the push
graph to run the required checks. This requires corresponding changes
to the mergify config to consider either of complete-pr or complete-push
as good enough to merge a PR.
| mobile/android/.mergify.yml | diffblobblamehistory | |
| mobile/android/.taskcluster.yml | diffblobblamehistory |