From 63610d57df3cb0063d4185967871e81538a4b738 Mon Sep 17 00:00:00 2001 From: dingo Date: Mon, 10 Aug 2026 17:32:05 +0700 Subject: [PATCH] ci: give this workflow a name of its own, so it stops cancelling upstream's Both files said `name: CI`. The concurrency group is built from ${{ github.workflow }}, which is that name, so the two workflows shared a group and cancelled each other on every push -- whichever started second would be the only one that ever reported a result. The compositor and session forks already say HyprCosmic for the same reason; this one was missed when it was renamed. --- .github/workflows/hyprcosmic.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/hyprcosmic.yml b/.github/workflows/hyprcosmic.yml index 50a4312..14d9f37 100644 --- a/.github/workflows/hyprcosmic.yml +++ b/.github/workflows/hyprcosmic.yml @@ -6,7 +6,11 @@ # text does not care which distribution it is on -- what matters there is whether # generated files are still in step with their generator, which is a single # question with a single answer. -name: CI +# The name is not "CI", which is upstream's ci.yml. Two workflows sharing a name +# share `${{ github.workflow }}`, and the concurrency group below is built from +# it -- they would cancel each other on every push, and whichever started second +# would be the only one that ever reported. +name: HyprCosmic on: push: