mirror of

Common settings (all editions) for Garuda Linux

Go to file

BluishHumility 8c2074e7f0 feat(pacseek): use -R instead of -Rns for pacman remove Use -R instead of -Rns for Pacman remove. Leaving the "s" out of it seems like a more prudent option, which I think we should opt for if users are going to be using this tool to remove packages. The advanced users who prefer the more aggressive behavior can change the config on their own. The "n" option shouldn't be part if it either way; I feel like a lot of people do not understand what this flag actually is.		2024-04-08 22:25:31 -04:00
.gitlab	feat: add information, ci checking commit message and remove PKGBUILD	2023-11-07 15:57:09 +01:00
etc	feat(pacseek): use -R instead of -Rns for pacman remove	2024-04-08 22:25:31 -04:00
usr	fix(zram-generator.conf): remove depreciated config options	2023-12-15 23:45:07 -05:00
.cz.yaml	ci: automate releases via pushing tags	2023-11-19 14:34:33 +01:00
.gitlab-ci.yml	ci: fix pip refusing to install any package	2023-12-11 14:04:19 -05:00
LICENSE	feat: add information, ci checking commit message and remove PKGBUILD	2023-11-07 15:57:09 +01:00
README.md	docs: add badges	2023-11-19 15:05:19 +01:00

README.md

Garuda Linux common settings

Found any issue?

If any packaging issues occur, don't hesitate to report them via our issues section of our PKGBUILD repo. You can click here to create a new one.
If issues concerning the configurations and settings occur, please open a new issue on this repository. Click here to start the process.

How to contribute?

We highly appreciate contributions of any sort! 😊 To do so, please follow these steps:

Create a fork of this repository.
Clone your fork locally (short git tutorial).
Add the desired changes to PKGBUILDs or source code.
Commit using a conventional commit message and push any changes back to your fork. This is crucial as it allows our CI to generate changelogs easily.
- The commitizen application helps with creating a fitting commit message.
- You can install it via pip as there is currently no package in Arch repos: pip install --user -U Commitizen.
- Then proceed by running cz commit in the cloned folder.
Create a new merge request at our main repository.
Check if any of the pipeline runs fail and apply eventual suggestions.

We will then review the changes and eventually merge them.

Where is the PKGBUILD?

The PKGBUILD can be found in our PKGBUILDs repository. Accordingly, packaging changes need to be happening over there.

How to deploy a new version?

To deploy a new version, pushing a new tag is sufficient. The deployment will happen automatically via the PKGBUILDs repo's pipelines, which check half-hourly for the existance of a more recent tag.