From a50b6a1e467f343d7bbd771879fb950e8debcae7 Mon Sep 17 00:00:00 2001
From: Timo Wilken
Date: Fri, 3 Nov 2023 23:03:21 +0100
Subject: Remove unused `act' package

---
 tw/packages/ci.scm | 25 -------------------------
 1 file changed, 25 deletions(-)

(limited to 'tw/packages')

diff --git a/tw/packages/ci.scm b/tw/packages/ci.scm
index f9bac3ca..d9edb83f 100644
--- a/tw/packages/ci.scm
+++ b/tw/packages/ci.scm
@@ -132,28 +132,3 @@ native Consul and Vault integrations.")
 HashiCorp Nomad jobs that provides realtime feedback and detailed failure
 messages upon deployment issues.")
     (license license:mpl2.0)))
-
-(define-public act-bin
-  (package
-    (name "act")
-    (version "0.2.45")
-    (home-page "https://github.com/nektos/act")
-    (source
-     (origin
-       (method url-fetch/tarbomb)
-       (uri (string-append home-page "/releases/download/v"
-                           version "/act_Linux_x86_64.tar.gz"))
-       (sha256 (base32 "12mvs4pylflgii4plqz3377lflz71q3dz2hi7j6hmr4a574v76zj"))))
-    (build-system copy-build-system)
-    (arguments
-     `(#:install-plan '(("act" "bin/"))))
-    (synopsis "Run your GitHub Actions locally")
-    (description "When you run act it reads in your GitHub Actions from
-@samp{.github/workflows/} and determines the set of actions that need to be
-run.  It uses the Docker API to either pull or build the necessary images, as
-defined in your workflow files and finally determines the execution path based
-on the dependencies that were defined.  Once it has the execution path, it
-then uses the Docker API to run containers for each action based on the images
-prepared earlier.  The environment variables and filesystem are all configured
-to match what GitHub provides.")
-    (license license:expat)))
-- 
cgit v1.2.3