Commit Graph

19 Commits

Author SHA1 Message Date
Aitor Perez 07adc3e571
Remove Bazel files 2025-03-13 13:42:34 +00:00
Michael Klishin a4f9babe2d
Update Mergify for v4.1.x
Pair: @the-mikedavis
(cherry picked from commit 1af6c4d2f4)
2025-02-10 10:33:19 -05:00
Michael Klishin e6da989e00 Mergify: re-introduce multi-branch backports
to both v4.0.x and v3.13.x at the moment.
2024-07-19 01:04:04 -04:00
Michael Klishin 599727ab22 Revisit Mergify settings
* Add v4.0.x
 * Drop more complex workflows/backport rules we
   do not really use in practice
2024-07-11 10:01:19 -04:00
Rin Kuryloski 8d1ecacb02 Update mergify for v3.13.x branch
The way this was done
1. find replace "v3.12.x" with "v3.13.x"
2. find replace "v3.11.x" with "v3.12.x"
3. find replace "v3.10.x" with "v3.11.x"
4. find replace "v3.9.x" with "v3.10.x"

"v3.10.x" was left in for simplicity, in case we need a 4 branch
cascade again
2024-03-13 11:19:31 +01:00
Rin Kuryloski c51195d4c9 Revert "Actions, Mergify: 3.13 is in, 3.10, 3.9 are out"
This reverts commit f936919cc0.
2024-03-13 11:14:42 +01:00
Michael Klishin f936919cc0 Actions, Mergify: 3.13 is in, 3.10, 3.9 are out 2024-02-24 20:06:19 -05:00
Rin Kuryloski e1129f6b8c Update the mergify config to account for v3.12.x branch 2023-02-14 16:25:31 +01:00
Rin Kuryloski 0ab453e09d Update GitHub Actions and Mergify for branch rename 2022-08-16 09:40:26 +02:00
Rin Kuryloski c2a72a1ded Remove the auto-commenting about build systems on PRs
The noise they add does not seem useful to me. Additionally, they
appeared to be defined slightly incorrectly for some cases.
2022-07-28 14:27:51 +02:00
Rin Kuryloski 477f526c35 Update mergify config to account for v3.11.x branch 2022-07-27 16:45:21 +02:00
Philip Kuryloski c9c5dcdfc9 Small tweak to automated PR comments by mergify 2022-03-16 12:16:50 +01:00
Philip Kuryloski 195b419706 Tweak the mergify comments to be less agressive 2022-03-11 17:24:55 +01:00
Philip Kuryloski fce41f0bfd Fixup message content in mergify config 2022-03-11 11:08:45 +01:00
Philip Kuryloski 4384034593 Add new rules to mergify config
New rules to automatically comment on a PR if it modifies bazel but
not make, or vice versa, as this might be a case where dependency
versions are not kept in sync
2022-03-11 11:01:03 +01:00
Philip Kuryloski 06d7c3fa84 GitHub Actions updates for the new v3.10.x branch 2022-01-11 16:47:46 +01:00
Philip Kuryloski 0dafe70005 Attempt to correct Mergify config for cascaded backports 2021-09-10 15:28:36 +02:00
Philip Kuryloski 0d6372159e Add Mergify config to backport based on label
A PR labeled with `backport-v3.9.x` will be cloned to the v3.9.x
branch automatically upon merge. `backport-v3.8.x` does the same for
v3.8.x
2021-09-07 09:02:06 +02:00
Philip Kuryloski 68872c4959 Add an initial mergify.io configuration 2021-08-03 12:04:30 +02:00