fix: switch over to usign `active-git instead of active-gitlab`

.forgejo/workflows/deploy.yaml

@@ -37,7 +37,7 @@ jobs:
 #      - run: colmena build -v --on @active-core
 #      - run: colmena build -v --on @active
 #      - run: colmena build -v --on @active-ext
-#      - run: colmena build -v --on @active-gitlab
+#      - run: colmena build -v --on @active-git
 
   deploy_dns:
     runs-on: nix

.forgejo/workflows/deploy_forgejo.yaml

@@ -8,5 +8,5 @@ jobs:
     runs-on: nix
     steps:
       - uses: actions/checkout@v4
-      - run: colmena apply -v --on @active-gitlab --show-trace
+      - run: colmena apply -v --on @active-git --show-trace
         shell: bash

.gitlab-ci.yml

@@ -124,7 +124,7 @@ build:
     - colmena build -v --on @active-core
     - colmena build -v --on @active
     - colmena build -v --on @active-ext
-    - colmena build -v --on @active-gitlab
+    - colmena build -v --on @active-git
 
 # dns always has to be deployed first
 deploy_dns:
@@ -167,5 +167,5 @@ deploy_gitlab:
   <<: *deployment
   stage: deploy_gitlab
   script:
-    - colmena apply -v --on @active-gitlab
+    - colmena apply -v --on @active-git
   when: manual

README.md

@@ -43,7 +43,7 @@ colmena build --on @active-dns
 Deploying is putting (apply-ing) the config tat was built onto the server, there is no need to build first, it will automatically do so.
 
 While the ***recommended way of deploying is using the CI/CD process*** there are times when you will have to manually deploy the config.  
-One such case is the ``@active-gitlab`` group if either Gitlab or Gitlab-runner got updated.  
+One such case is the ``@active-git`` group if either Gitlab or Gitlab-runner got updated.  
 Another is if ye have fecked up DNS.
 
 Your ``~/.ssh/config``  should be set up as follows and you should be a member of ``skynet-admins-linux``
@@ -60,10 +60,10 @@ Then you can run the following commands like so:
 ```shell
 colmena apply
 colmena apply --on @active-dns
-colmena apply --on @active-gitlab
+colmena apply --on @active-git
 ```
 
-The CI/CD pipeline has a manual job that can be triggered to update ``@active-gitlab`` if you know it wont cause issues.
+The CI/CD pipeline has a manual job that can be triggered to update ``@active-git`` if you know it wont cause issues.
 
 ### Agenix
 

machines/glados.nix

@@ -35,7 +35,7 @@ in {
     targetPort = 22;
     targetUser = null;
 
-    tags = ["active-gitlab"];
+    tags = ["active-git"];
   };
 
   services.skynet = {

machines/wheatly.nix

@@ -33,7 +33,7 @@ in {
     targetPort = 22;
     targetUser = null;
 
-    tags = ["active-gitlab"];
+    tags = ["active-git"];
   };
 
   services.skynet = {