fix: run flake checks on Gitlab CI with org-wide runner - GitHub runn…

…ers were hitting limits easily

.gitlab-ci.yml

@@ -0,0 +1,10 @@
+---
+stages: [check]
+check:
+  stage: check
+  image: nixpkgs/nix-flakes:latest
+  script:
+    - sed -i 's&../secrets/secrets.json&../../assets/dummy.json&g' ./nixos/modules/garuda-lib.nix
+    - nix flake check
+  rules:
+    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH

.gitlab/CODEOWNERS

@@ -0,0 +1 @@
+* @garuda-linux

README.md

@@ -1,14 +1,15 @@
 # Garuda Linux server configurations
 
-[![built with nix](https://img.shields.io/static/v1?logo=nixos&logoColor=white&label=&message=Built%20with%20Nix&color=41439a)](https://builtwithnix.org) [![run nix flake check](https://github.com/garuda-linux/infrastructure-nix/actions/workflows/flake_check.yml/badge.svg?branch=main)](https://github.com/garuda-linux/infrastructure-nix/actions/workflows/flake_check.yml) [![deploy docs](https://github.com/garuda-linux/infrastructure-nix/actions/workflows/pages.yml/badge.svg)](https://github.com/garuda-linux/infrastructure-nix/actions/workflows/pages.yml)
+[![built with nix](https://img.shields.io/static/v1?logo=nixos&logoColor=white&label=&message=Built%20with%20Nix&color=41439a)](https://builtwithnix.org) [![deploy docs](https://github.com/garuda-linux/infrastructure-nix/actions/workflows/pages.yml/badge.svg)](https://github.com/garuda-linux/infrastructure-nix/actions/workflows/pages.yml)
 
 ## General information
 
 - Our current infrastructure is hosted in one of [these](https://www.hetzner.com/dedicated-rootserver/ax102).
 - The only other server not being contained in this dedicated server is our mail server.
 - Both servers are being backed up to Hetzner storage boxes via [Borg](https://www.borgbackup.org/).
 - After multiple different setups, we settled on [NixOS](https://nixos.org/) as our main OS as it provides reproducible and atomically updated system states
-- Most (sub)domains are protected by Cloudflare while also making use of its caching feature. Exemptions are services such as our mail server and parts violating Cloudflares rules such as proxying Piped content.
+- Most (sub)domains are protected by Cloudflare while also making use of its caching feature.
+  Exemptions are services such as our mail server and parts violating Cloudflares rules such as proxying Piped content.
 
 ## Quick links