Wolfgang Walther 17eb6dcb27 workflows: move eval from push to queue ... Running eval in the merge queue prevents eval failures after merging multiple PRs with semantic merge conflicts. It's also the base for allowing more sophisticated checks about rebuild counts in the merge queue later. When branches are directly pushed to, such as for periodic merges, this will not run Eval immediately. However, the next PR will run it as part of its Eval step and will cache the results. Any further PR will then benefit from the same caching again. This also avoids running Eval twice when pushing to staging-next or haskell-updates, where a PR is open at the same time. Here, the PR's Eval still runs on the push, of course.		2025-10-14 19:47:20 +02:00
..
actions/checkout	actions/checkout: update input descriptions	2025-08-22 17:30:44 +01:00
ISSUE_TEMPLATE	ISSUE_TEMPLATE/03_bug_report_nixos: remove git blame	2025-09-12 19:49:20 +02:00
workflows	workflows: move eval from push to queue	2025-10-14 19:47:20 +02:00
dependabot.yml	treewide: run yamlfmt	2025-06-12 14:46:42 +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	treewide: run yamlfmt	2025-06-12 14:46:42 +02:00
labeler-no-sync.yml	.github/labeler-no-sync: add backport label to action changes	2025-08-22 18:50:07 +02:00
labeler.yml	.github/labeler.yml: add pop-launcher in COSMIC topic	2025-09-28 09:40:32 -03:00
PULL_REQUEST_TEMPLATE.md	.github/PULL_REQUEST_TEMPLATE.md: fix typo	2025-07-20 09:27:04 -04:00
STALE-BOT.md