Actionless Loveless

i never liked the dependency on those proprietary third-party services i am thinking - could we just replace it to a bash one-liner which would compare coverage % in the...

i'd like to keep the check, as it helps to avoid pointless conversations on trying to convince people to cover their new features with some tests :) those tools are...

> So we are doomed to wait for someone else... btw for some parts of the infra only @blueyed have the access, not even anyone else, so we have our...

https://github.com/awesomeWM/awesome/actions/runs/10548999597/job/29229634679?pr=3943

yup, that's a problem, but how longer release period is helping to avoid that? also that works in both directions - for bugs/regressions found in the release users wouldn't get...

even if someone would - fixing and getting them all merged might take 0.5 year or more (https://github.com/awesomeWM/awesome/issues?page=1&q=is%3Aopen+is%3Aissue+milestone%3Av4.4)

if you wanna discuss further backport-releases such as 4.3.x please make a separate topic, as this one is functionally a different thing

thanks for submitting, i found small issue right from the description (and left a separate comment), i'll start reviewing the code itself later on in upcoming days or mb even...

and also the test is failing: - /home/runner/work/awesome/awesome/tests/test-awesomerc.lua: Error: running function for step 13/18 (@3): /home/runner/work/awesome/awesome/tests/test-awesomerc.lua:289: assertion failed!

regarding keygrabber question, i'll need first to understand: 1) what was the initial intention of returning it there 2) why it's not possible to do it anymore