Skip to content

Conversation

@duraseb
Copy link

@duraseb duraseb commented Nov 30, 2025

🙏 Thank you for sending in a pull request, here's some tips to get started!

❌ (Please delete all these tips and replace them with your text) ❌

  • Before starting on some new big chunk of code, it it is optional but highly recommended to open an issue first
    to say "Hey, I think this idea X should be implemented and I'm starting work on it. My general plan is Y, any feedback
    is appreciated." This will allow other devs to potentially save you time by not accidentially duplicating work etc...
  • Please do not check in files that don't have real changes
  • Please do not reformat lines that you didn't have to change the code on
  • We recommend using the Visual Studio Code editor along with the 'Trunk Check' extension (In beta for windows, WSL2 for the linux version),
    because it automatically follows our indentation rules and its auto reformatting will not cause spurious changes to lines.
  • If your PR fixes a bug, mention "fixes #bugnum" somewhere in your pull request description.
  • If your other co-developers have comments on your PR please tweak as needed.
  • Please also enable "Allow edits by maintainers".
  • Please do not submit untested code.
  • If you do not have the affected hardware to test your code changes adequately against regressions, please indicate this, so that contributors and commnunity members can help test your changes.
  • If your PR gets accepted you can request a "Contributor" role in the Meshtastic Discord

🤝 Attestations

  • I have tested that my proposed changes behave as described.
  • I have tested that my proposed changes do not cause any obvious regressions on the following devices:
    • Heltec (Lora32) V3
    • LilyGo T-Deck
    • LilyGo T-Beam
    • RAK WisBlock 4631
    • Seeed Studio T-1000E tracker card
    • Other (please specify below)

@CLAassistant
Copy link

CLAassistant commented Nov 30, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
11 out of 12 committers have signed the CLA.

✅ jp-bennett
✅ Xaositek
✅ Stary2001
✅ HarukiToreda
✅ RikerZhu
✅ Quency-D
✅ NomDeTom
✅ rbomze
✅ Donix212
✅ RCGV1
✅ thebentern
❌ duraseb
You have signed the CLA already but the status is still pending? Let us recheck it.

@duraseb duraseb force-pushed the signal_based_routing branch from 3dcd4d1 to 5771c0c Compare December 1, 2025 12:46
jp-bennett and others added 6 commits December 2, 2025 05:48
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@duraseb duraseb force-pushed the signal_based_routing branch from 8d22096 to 86dfa56 Compare December 5, 2025 01:36
github-actions bot and others added 21 commits December 5, 2025 10:41
* Remove native from the build, and remove the required permissions

* Delete .github/workflows/build_one_arch.yml

Its borken and not really needed. one_target is the goal.
* Swap the GPS serial port pins.

* Trunk fixes

---------

Co-authored-by: Jason P <[email protected]>
Co-authored-by: Ben Meadors <[email protected]>
This seems to be a potential source of unintended screen wakes.
Update preprocessor directive to require both HAS_WIFI and MESHTASTIC_EXCLUDE_WIFI conditions.
* Add initial support for Hackaday Communicator

* Fork it!

* Trunk

* Remove unused elements from the HackadayCommunicatorKeyboard

* Don't divide by zero.
Signed-off-by: kur1k0 <[email protected]>
Co-authored-by: Ben Meadors <[email protected]>
Co-authored-by: Jonathan Bennett <[email protected]>
* Initial Chatter 2.0 fix for baseUI

* trunk fix

---------

Co-authored-by: Jason P <[email protected]>
…c#8811)

* Plain RAK4631 should not compile EInk and TFT display code

* Add USE_TFTDISPLAY to variant files.

* Derp

* Undo the platformio.ini changes to heltec_v4

* Drop unneeded src_filter lines

---------

Co-authored-by: Jonathan Bennett <[email protected]>
Co-authored-by: Jason P <[email protected]>
…114 variant, due to power leakage of 2.9mA in off state. See bug meshtastic#8801 (meshtastic#8800)

Co-authored-by: Ben Meadors <[email protected]>
…ing insights, including detailed messages for unicast and broadcast handling, as well as route calculations.
@duraseb duraseb force-pushed the signal_based_routing branch from 1ab7822 to 11f5c94 Compare December 8, 2025 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.