nixpkgs/.github
Wolfgang Walther d2ff68b564
workflows/{eval,labels}: allow testing labeling job in forks
A while ago, I added those "owner == NixOS" conditions, because I
couldn't figure out why my fork kept failing those jobs, even though I
had set up the apps correctly.

Turns out, that when a label doesn't exist, those actions try to
implicitly create it. But to do that, they actually need write
permissions on the *issues* endpoint, the pull-requests endpoint is not
enough. Even though the docs state otherwise.

Thus, adding those permissions. This will also lead to new labels being
created when they are added via code (for example in
.github/labels.yml), even when they had not been created, yet. Labels
created this way will initially be grayish color and without description
- but we can always add those later, there is no point in failing
pipelines for everyone in that case.
2025-05-26 18:06:24 +02:00
..
actions/get-merge-commit workflows: checkout nixpkgs in get-merge-commit action 2025-05-25 15:14:23 +02:00
ISSUE_TEMPLATE ISSUE_TEMPLATES: update releases following 25.11's branch-off 2025-05-16 20:27:35 -03:00
workflows workflows/{eval,labels}: allow testing labeling job in forks 2025-05-26 18:06:24 +02:00
dependabot.yml .github/dependabot.yml: disable default labels 2025-05-05 17:15:19 +02:00
ISSUE_TEMPLATE.md ISSUE_TEMPLATE.md: clear the blank issue template 2025-01-12 16:01:56 -03:00
labeler-development-branches.yml workflows/labeler: fix repo owner condition 2025-05-04 18:52:43 +02:00
labeler-no-sync.yml labels: Automatically label CI changes for backport to 25.05 2025-05-16 20:53:25 +02:00
labeler.yml labels: no CI label for OWNERS changes 2025-05-11 12:20:07 +02:00
PULL_REQUEST_TEMPLATE.md 25.11 is Xantusia 2025-05-16 19:21:55 +02:00
STALE-BOT.md .github/stale bot: stop commenting 2022-04-30 08:30:08 -07:00
stale.yml .github/stale bot: stop commenting 2022-04-30 08:30:08 -07:00