quiK/NaxGCC-FW

Author	SHA1	Message	Date
Naxdy	8a0760a620	chore: clippy concurrency (#10 ) Reviewed-on: NaxdyOrg/NaxGCC-FW#10	2024-04-08 21:25:02 +00:00
Naxdy	fd9f9b533f	chore: add v1.0.0 changelog	2024-04-08 23:04:56 +02:00
Naxdy	ba7164dd9c	feat(ci): add workflow for stable releases	2024-04-08 22:55:23 +02:00
Naxdy	702cbe5eb0	add mode to further improve input latency while maintaining accuracy (#8 ) This feels even hackier than consistency mode... we hold off on writing USB reports until the button state actually changes. Passes the input integrity benchmark with ~99.6%, but that doesn't mean much since the challenge is preserving input integrity for inputs less than 8.33ms apart. Current rate limiter looks good from initial measurements, so will probably merge this at some point and leave it up to users to try the mode out or not. For now, I'd still recommend regular consistency mode, it's still hacky, but way less than this. Also, not breaking because the new enum for input consistency mode is backward compatible with the bool. Reviewed-on: NaxdyOrg/NaxGCC-FW#8	2024-04-08 20:53:23 +00:00
Naxdy	c2e4066125	chore: cancel previous clippy runs if need be	2024-04-08 22:40:38 +02:00
Naxdy	c43e66f91d	chore: clarify nightly	2024-04-05 23:46:05 +02:00
Naxdy	be2f3cb755	chore: add nightly warning	2024-04-05 13:04:53 +02:00
Naxdy	f4de1326a5	change(project): use https for git resolution	2024-04-05 12:39:39 +02:00
Naxdy	5cabeeb109	fix(ci): scan host key in clippy flow	2024-04-05 12:37:12 +02:00
Naxdy	bb2184fa29	chore(ci): use public binary cache	2024-04-05 12:14:22 +02:00
Naxdy	2f49357029	chore: refactor according to clippy & clean up config (#6 ) Reviewed-on: NaxdyOrg/NaxGCC-FW#6	2024-04-03 16:53:52 +00:00
Naxdy	0320c72d3a	feat(ci): (re-)generate tag	2024-03-26 21:21:34 +01:00
Naxdy	45e23b3d41	change(project): switch to forgejo workflows	2024-03-26 21:19:49 +01:00

13 commits