Jorropo and GitHub
beb268ff25
Revert "add a .clang-format file ( #9154 )" ( #9172 )
...
I thought git would be smart enough to understand all the whitespace changes but even with all the flags I know to make it ignore theses it still blows up if there are identical changes on both sides.
I have a solution but it require creating a new commit at the merge base for each conflicting PR and merging it into develop.
I don't think blowing up all PRs is worth for now, maybe if we can coordinate this for V3 let's say.
This reverts commit 0d11331d18
2026-01-04 05:15:53 -06:00
Jorropo and GitHub
0d11331d18
add a .clang-format file ( #9154 )
2026-01-03 14:19:24 -06:00
8fdba1f1e2
RTC: PCF85063 support, port to SensorLib 0.3.1 ( #8061 )
...
* RTC: PCF85063 support, port to SensorLib 0.3.1
* Tidy up defines
* Remove RTC/PCF8563 mentions from unrelated variants
* Bump SensorLib 0.3.2
* Use SensorRtcHelper
* Consistent warning message
* Fix oversight
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com >
---------
Co-authored-by: Manuel <71137295+mverch67@users.noreply.github.com >
Co-authored-by: Ben Meadors <benmmeadors@gmail.com >
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com >
2025-12-20 19:10:21 -06:00
Austin and GitHub
96c42229b0
Renovate all the things ( #8994 )
2025-12-17 11:05:48 -06:00
Austin and GitHub
ed77ba5612
Replace PIO fuzzy version matches (reproducible builds) ( #8984 )
...
This change does not introduce version *changes*, but simply "updates" to the version already being referenced by the fuzzy-match (^)
2025-12-15 19:48:34 -06:00
Austin and GitHub
eafa8c7b47
PIO: Fix ESP32 sub-variant inheritance ( #8983 )
2025-12-15 19:04:03 -06:00
Austin and GitHub
4f895f744b
Take control of our PRs! ( #7445 )
2025-07-24 06:13:23 -05:00
Austin and GitHub
475cfe4af2
ESP32s3: Migrate variants to new structure ( #7343 )
2025-07-20 16:47:37 -05:00
JorropoandGitHub
AustinandGitHub