Commit Graph

23 Commits

Author SHA1 Message Date
yaya
fd782901e5 .github/labeler-no-sync: Remove backport release-25.11
NixOS 25.11 is end-of-life.
2026-07-01 13:55:42 +02:00
yaya
41a5348c15 .github: Add release-26.05 CI config 2026-05-24 14:51:41 +02:00
Matt Sturgeon
cbf9173b17 github/labeler: fix auto-tag backport for .github/actions
.github/actions/* does not match deeply nested files like
.github/actions/checkout/action.yml

Instead, we need a recursive glob like **/*
2026-01-22 01:55:56 +00:00
Michael Daniels
a6ec4bf808 {README.md,.github/*}: remove/replace references to 25.05 release 2026-01-01 21:23:07 -05:00
Matt Sturgeon
20ab35ae0c github/labeler: auto-tag backports for labeler
The labeler reads its config from the PR's base branch. Therefore, its
config files need to be kept in sync across development branches, like
other CI files.
2025-12-20 18:19:29 +00:00
Michael Daniels
e30855a4d4 github/labeler: do not auto-tag backports for backport
E.g. #472010, #472185
2025-12-18 17:15:17 -05:00
Wolfgang Walther
fb0fb7420f .github/labeler-no-sync: add release-25.11 for CI stuff 2025-11-25 11:23:38 +01:00
Wolfgang Walther
d78de15627 workflows/bot: rename from labels
This workflow / script is already doing more than must labeling: it's
already auto-closing package request issues.

Since we're going to migrate the nixpkgs-merge-bot into this workflow,
we'll rename things to a more generic name.
2025-11-01 15:24:09 +01:00
Wolfgang Walther
0ace36a3da .github/labeler-no-sync: backport changes to github-teams
Changes to this auto-generated file need to be backported automatically,
to keep maintainer pings for teams functional on stable branches.
2025-10-28 12:13:54 +01:00
Wolfgang Walther
f5267c408d .github/labeler-no-sync: add backport label to action changes
Sometimes *only* the action is changed as well.
2025-08-22 18:50:07 +02:00
Leona Maroni
e83d9fbf16 .github/labeler: remove "backport release-24.11" auto label
24.11 is unmaintained.
2025-07-01 15:27:02 +02:00
Wolfgang Walther
66981875e8 treewide: run yamlfmt
This applies changes from running yamlfmt with the `retain_line_breaks`
formatting option enabled.
2025-06-12 14:46:42 +02:00
Wolfgang Walther
252659081e labels: automatically add labels for 24.11 on CI PRs
The chained backport unstable -> 25.05 -> 24.11 became too annoying for
me.
2025-06-02 18:05:08 +02:00
Wolfgang Walther
ae32b63ccb labels: Automatically label CI changes for backport to 25.05 2025-05-16 20:53:25 +02:00
Wolfgang Walther
12a7f01211 Revert "labels: add backport label for automatic browser updates"
This reverts commit 189dd476d4.
2025-05-05 17:54:44 +02:00
Wolfgang Walther
5388d4f37b Revert "labels: fix backport labels for CI workflows"
This reverts commit 54331e1101.
2025-05-05 17:19:07 +02:00
Wolfgang Walther
54331e1101 labels: fix backport labels for CI workflows
This broke in #402304.

According to the upstream docs it's possible to use the same label
multiple times, this should work.
2025-05-05 17:08:05 +02:00
Wolfgang Walther
f1b0c199ea labels: run keep-sorted 2025-05-03 19:15:14 +02:00
Wolfgang Walther
e357e6e1f9 labels: keep them sorted
We already tried and mostly succeeded - but we can do better.
2025-05-03 19:15:11 +02:00
Wolfgang Walther
189dd476d4 labels: add backport label for automatic browser updates
Browser updates should always be backported for security reasons, so
let's make our life a bit easier by adding the backport label for
r-ryantm's PRs automatically.
2025-05-01 12:12:04 +02:00
Wolfgang Walther
9c33953ba2 .github/labeler-no-sync: fix backport labels
Matching on !ci/OWNERS was a mistake, because it's matching *every* PR
with a change to a non-OWNERS file.

This is not fixable with negation rules in the labeler, but we can take
advantage of the fact that OWNERS doesn't have a "." in its name.

Also, we used the wrong label...
2025-02-01 17:20:32 +01:00
Peder Bergebakken Sundt
15b3e2d0fe .github/labeler-no-sync.yml: automatically add backport label for PRs touching ci/ 2025-01-20 12:49:05 +01:00
Peder Bergebakken Sundt
8ed4f7b5a6 workflows/labels: add a sync-labels: false step, migrate some rules 2025-01-20 12:35:38 +01:00