dependabot[bot]
2f2a95ddcc
build(deps): bump cachix/cachix-action from 15 to 16
...
Bumps [cachix/cachix-action](https://github.com/cachix/cachix-action ) from 15 to 16.
- [Release notes](https://github.com/cachix/cachix-action/releases )
- [Commits](ad2ddac53f...0fc020193b
2025-03-17 11:37:30 +00:00
FliegendeWurst
ad9c0d717e
ISSUE_TEMPLATE: avoid using maintainer usernames as headings (part 2)
2025-03-14 09:49:10 +01:00
ash
3f7297b749
ISSUE_TEMPLATE: avoid using maintainer usernames as headings
2025-03-07 08:39:16 +00:00
dependabot[bot]
94816e8c96
build(deps): bump actions/create-github-app-token from 1.11.5 to 1.11.6
...
Bumps [actions/create-github-app-token](https://github.com/actions/create-github-app-token ) from 1.11.5 to 1.11.6.
- [Release notes](https://github.com/actions/create-github-app-token/releases )
- [Commits](0d564482f0...21cfef2b49
2025-03-03 11:17:16 +00:00
Wolfgang Walther
f78a1e6d34
build(deps): bump korthout/backport-action from 3.1.0 to 3.2.0 ( #384747 )
2025-02-27 19:41:10 +01:00
dependabot[bot]
a38730c806
build(deps): bump actions/upload-artifact from 4.6.0 to 4.6.1
...
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact ) from 4.6.0 to 4.6.1.
- [Release notes](https://github.com/actions/upload-artifact/releases )
- [Commits](65c4c4a1dd...4cec3d8aa0
2025-02-24 12:19:54 +00:00
dependabot[bot]
d1b76b4b7c
build(deps): bump korthout/backport-action from 3.1.0 to 3.2.0
...
Bumps [korthout/backport-action](https://github.com/korthout/backport-action ) from 3.1.0 to 3.2.0.
- [Release notes](https://github.com/korthout/backport-action/releases )
- [Commits](be567af183...436145e922
2025-02-24 12:19:51 +00:00
r-vdp
707565040a
.github/workflows: build the nixos manual also when doc/ changed
...
We import things like the nixpkgs release notes, and the css and js
files from doc/ into nixos/doc/, so building the nixos manual whenever
doc/ was modified, avoids failures reaching master.
2025-02-19 11:32:17 +01:00
dependabot[bot]
f66585fd39
build(deps): bump actions/create-github-app-token from 1.11.3 to 1.11.5
...
Bumps [actions/create-github-app-token](https://github.com/actions/create-github-app-token ) from 1.11.3 to 1.11.5.
- [Release notes](https://github.com/actions/create-github-app-token/releases )
- [Commits](67e27a7eb7...0d564482f0
2025-02-17 11:47:47 +00:00
Wolfgang Walther
e3dcb81033
.github/ISSUE_TEMPLATE: fix fields for package request ( #380800 )
2025-02-16 13:36:48 +01:00
Silvan Mosberger
ec32f93eb2
workflows/eval-lib-tests: Run on maintainer changes
...
The lib tests also check maintainers, not doing so can cause problems: https://github.com/NixOS/nixpkgs/pull/379894
2025-02-12 09:45:25 +05:30
dependabot[bot]
95e123c783
build(deps): bump actions/create-github-app-token from 1.11.1 to 1.11.3
...
Bumps [actions/create-github-app-token](https://github.com/actions/create-github-app-token ) from 1.11.1 to 1.11.3.
- [Release notes](https://github.com/actions/create-github-app-token/releases )
- [Commits](c1a285145b...67e27a7eb7
2025-02-10 11:50:07 +00:00
Gavin John
9394afabbc
.github/ISSUE_TEMPLATE: fix fields for package request
2025-02-09 18:44:09 -08:00
Silvan Mosberger
353c0a7b6f
workflows/eval: fail hard without target run ( #378909 )
2025-02-04 10:36:53 +01:00
Tristan Ross
e45cf3532d
.github/labeler.yml: add teams topic ( #378233 )
2025-02-02 21:56:21 -08:00
Wolfgang Walther
93df51fa33
workflows/eval: rename BASE_SHA to TARGET_SHA
...
To be in line with the terminology introduced in the README.md in the
same folder.
2025-02-02 20:17:33 +01:00
Wolfgang Walther
86a38d48fb
workflows/eval: fail hard without target run
...
Without a target run, we won't get any rebuild labels, rebuild counts or
maintainer pings. This might have been correct before #373935 , but by
now we run eval on all commits on the target branch, so we should treat
it as a failure if we can't find the run.
2025-02-02 20:17:09 +01: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
Wolfgang Walther
06fa362486
workflows/eval: no maintainer reviews in draft mode ( #372479 )
2025-02-01 11:58:50 +01:00
Wolfgang Walther
1a53a38d36
.github/labeler.yml: automatically add backport label for PRs touching ci/ ( #374921 )
2025-02-01 11:57:14 +01:00
Tristan Ross
eb14d1ba38
.github/labeler.yml: add teams topic
2025-01-31 01:20:35 -08: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
Silvan Mosberger
8e614ad4fa
ci: Format nixfmt command prominently ( #373939 )
2025-01-19 10:28:41 +01:00
Robert Hensing
c98e26ae4e
ci: Interpunction
...
The latter part is structurally a full sentence, if short.
2025-01-15 06:52:30 +01:00
Robert Hensing
3895dfe2cf
ci: Show example nixfmt command prominently
2025-01-15 06:51:53 +01:00
John Titor
38ebbf7c4f
workflows/periodic-merges: explicitly inherit the secrets
...
Apparently since we are callling a reusable workflow here, we need to explicitly pass the secrets. :(
2025-01-15 11:04:30 +05:30
John Titor
6ab6314d06
workflows/periodic-merges: use nixpkgs-ci's token
2025-01-15 10:29:29 +05:30
John Titor
f697628305
workflows/backport: switch to new variables
...
As per https://github.com/NixOS/org/issues/54 , new variables are now NIXPKGS_CI_APP_ID and NIXPKGS_CI_APP_PRIVATE_KEY.
2025-01-15 10:19:21 +05:30
Wolfgang Walther
21b5113509
workflows/eval: no maintainer reviews in draft mode
2025-01-13 20:48:05 +01:00
Silvan Mosberger
af0cd203ab
ISSUE_TEMPLATE: convert into YAML forms ( #368656 )
2025-01-13 19:17:58 +01:00
Silvan Mosberger
be67d6fb26
workflows/codeowners-v2: only run if github.repository_owner is NixOS ( #360286 )
2025-01-13 18:44:15 +01:00
dependabot[bot]
c254691a5b
build(deps): bump actions/upload-artifact from 4.5.0 to 4.6.0
...
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact ) from 4.5.0 to 4.6.0.
- [Release notes](https://github.com/actions/upload-artifact/releases )
- [Commits](6f51ac03b9...65c4c4a1dd
2025-01-13 11:45:12 +00:00
Fernando Rodrigues
5f291530a1
ISSUE_TEMPLATE: convert the build reproducibility issue template into an YAML form
...
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
2025-01-12 16:21:05 -03:00
Fernando Rodrigues
0375ee86f4
ISSUE_TEMPLATE: convert the feature requests (package, module, update, backport requests) into YAML forms
...
The out of date package report was split into two forms: an update request and a backport request.
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
2025-01-12 16:10:12 -03:00
Fernando Rodrigues
76881db85c
ISSUE_TEMPLATE: convert the missing documentation issue template into an YAML form
...
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
2025-01-12 16:09:28 -03:00
Fernando Rodrigues
9c605cfb70
ISSUE_TEMPLATE: convert the build failure template into an YAML form
...
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
2025-01-12 16:09:28 -03:00
Fernando Rodrigues
f3215665f0
ISSUE_TEMPLATE: convert the bug report template into three YAML forms
...
One for generic package issues, one for NixOS (Module)
issues, and one for Darwin-specific issues.
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
2025-01-12 16:09:07 -03:00
Fernando Rodrigues
c4433d3b4f
ISSUE_TEMPLATE: delete tracking_issue template
...
As discussed in #368656 .
Approved-by: Yohann Boniface <edhyjox@gmail.com>
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
2025-01-12 16:01:57 -03:00
Fernando Rodrigues
222f390e50
ISSUE_TEMPLATE.md: clear the blank issue template
...
This changes the blank issue template to a simple HTML comment telling
users to use the forms instead, while still allowing experienced
contributors to create free-form issues.
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
2025-01-12 16:01:56 -03:00
Wolfgang Walther
d725592cd1
workflows/periodic-merge: move fork condition to calling workflow
...
Apparently the skipping needs to happen on the calling workflow,
otherwise those workflows show up as "failed" in forks instead of
skipped.
2025-01-12 13:41:05 +01:00
Zhong Jianxin
973017d933
workflows/codeowners-v2: only run if github.repository_owner is NixOS
...
Failure on fork:
```
throw new Error("Input required and not supplied: app-id");
```
2025-01-11 21:14:39 +08:00
Silvan Mosberger
73a4ae3b3a
workflows: small refactors ( #371216 )
2025-01-11 12:28:20 +01:00
StrongSand94191
dc1758843d
.github: Fix capitalization in issue templates ( #368493 )
2025-01-11 12:12:56 +01:00
Wolfgang Walther
9ea74225cc
workflows: add README
...
This introduces some basic concepts used in these workflows and a common
terminology.
At the same time we remove some of the comments from various workflow
files, because they are assumed to be "general knowledge" through the
README.
2025-01-10 18:36:22 +01:00
Wolfgang Walther
3e9f5c05ea
workflows: rename baseSha to targetSha
...
We currently use two different "base" commits, but the same name. One of
them is the commit in which context the pull_request_target runs. The
other is the parent of the merge commit. Those are **not** necessarily
the same - see README introduced in the next commit for details.
Renaming one of them for clarity. Since the pull_request_target related
base commit is also called like that in GitHub Actions terminology, we
rename the other. The best I could come up with is "target".
2025-01-10 18:36:22 +01:00
Wolfgang Walther
ba09688dc8
workflows/periodic-merge: support merge bases in re-usable workflow
2025-01-10 18:36:22 +01:00
Wolfgang Walther
51b8ad2191
workflows/periodic-merge: create re-usable workflow
...
Less repetition, more consistency.
2025-01-10 18:36:22 +01:00
Wolfgang Walther
58f8c536c6
workflows/{editorconfig,nix-parse}: run against release branches
...
It seems odd to exclude PRs against release branches for those checks -
especially when not excluding PRs against staging-** variants at the
same time.
2025-01-10 18:36:22 +01:00
Wolfgang Walther
b64d5e1c0c
workflows: make checks work with non-NixOS repos
...
No need for that limitation, which only artifically limits test-ability
of CI in forks.
Some other workflows like backports, cherry-pick checks and periodic
merges are very specific to the release branches and don't need to be
run in forks.
2025-01-10 18:36:21 +01:00
