From 2c7e86ddcd8012bfae5956af89faef2983a1d3e8 Mon Sep 17 00:00:00 2001 From: Adam Fidel Date: Mon, 30 Dec 2024 22:03:25 -0600 Subject: [PATCH] chore: update build badges in README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7f46e2e..82ff166 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # HWE -[![build-39](https://github.com/ublue-os/hwe/actions/workflows/build-39.yml/badge.svg)](https://github.com/ublue-os/hwe/actions/workflows/build-39.yml) [![build-40](https://github.com/ublue-os/hwe/actions/workflows/build-40.yml/badge.svg)](https://github.com/ublue-os/hwe/actions/workflows/build-40.yml) +[![build-41](https://github.com/ublue-os/hwe/actions/workflows/build-41.yml/badge.svg)](https://github.com/ublue-os/hwe/actions/workflows/build-41.yml) [![build-40](https://github.com/ublue-os/hwe/actions/workflows/build-40.yml/badge.svg)](https://github.com/ublue-os/hwe/actions/workflows/build-40.yml) The purpose of these images is to provide [community Fedora images](https://github.com/ublue-os/main) with hardware enablement (ASUS and Surface) and Nvidia. This approach can lead to greater reliability as failures can be caught at the build level instead of the client machine. This also allows for individual sets of images for each series of Nvidia drivers, allowing users to remain current with their OS but on an older, known working driver. Performance regression with a recent driver update? Reboot into a known-working driver after one command. That's the goal!