Skip to content

[TEST] CI run for ExpressLRS/ExpressLRS-Configurator#800 - #2

Closed
Raffi1202 wants to merge 2 commits into
masterfrom
feature/firmware-output-folder
Closed

Raffi1202 wants to merge 2 commits into
masterfrom
feature/firmware-output-folder

Conversation

@Raffi1202

Copy link
Copy Markdown
Owner

Fork-internal test PR to run the CI workflows for the upstream pull request ExpressLRS#800. Not for merging.

–Raphael Hunziker added 2 commits August 20, 2026 07:40
Firmware built with the "Build" job type was copied into a temporary
folder and that folder was opened in the file explorer. Temporary
folders are cleaned up by the operating system, so users doing a WiFi
build had to move the binary out of an obscure path before it was gone.

The destination is now configurable in the settings screen:

- ask every time (default): a folder selection dialog is shown after
  every successful build
- always save into the same folder: firmware is copied there without
  further interaction
- temporary folder: previous behaviour

In the first two modes a folder named after the firmware is created in
the selected location, so builds do not overwrite each other, and the
file explorer is opened at the new location as before. Flashing jobs are
not affected.
Build artefacts are not always named after the device target: a WiFi
build produces a plain "firmware.bin.gz", which resulted in an output
folder called "firmware" that gives no hint about what is inside.

The renderer now passes the device target and the firmware version along
with the save request, so the folder becomes something like
"Happymodel_EP_2400_RX_via_WIFI-3.5.6". The firmware filename is still
used as a fallback when the target is unknown.
@Raffi1202 Raffi1202 closed this Sep 9, 2026
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.

1 participant