X Tutup
Skip to content

Disable autoupload by default in PIO builds#3545

Open
CapnBry wants to merge 1 commit intoExpressLRS:masterfrom
CapnBry:autoupload
Open

Disable autoupload by default in PIO builds#3545
CapnBry wants to merge 1 commit intoExpressLRS:masterfrom
CapnBry:autoupload

Conversation

@CapnBry
Copy link
Member

@CapnBry CapnBry commented Feb 19, 2026

Disables the "auto upload" function of the config-append step of a build, now only performed if "autoupload" is set in the cache file.

Details

In #3449 we added the saving of the appended hardware config when you're doing a build, and it auto uploads that config if you do a PIO upload action without prompting. In practice now that we're using it, this is an opportunity to forget that you have to do a "clean" operation and upload the wrong hardware config by mistake 😞

The autoupload function can be re-enabled in the cache json, any value that evaluates to true in python works:

image

Any other options?

I'd love to have some easier way to toggle this, so I'm open to other ideas but I think it may be best to just make it a default-off option in the config for now. I didn't want to add a user_define for it because that seems wrong and forces a full rebuild if you change them.

Apologies to @mha1 for all the dead hardware needing reflashing!

@CapnBry CapnBry added enhancement 🪄 New feature or request V4.1 🍑 labels Feb 19, 2026
@CapnBry CapnBry changed the title Don't autoupload unless autoupload key to true in cache json Disable autoupload by default in PIO builds Feb 19, 2026
@pkendall64
Copy link
Collaborator

Maybe we could wait for a period of time at the prompt before continuing with the default? I think that would give us the best of both worlds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement 🪄 New feature or request V4.1 🍑

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

X Tutup