Hi...
I'm new to github so apologies if this is a dumb query, but...
I followed the instructions in this doc:
https://docs.espressif.com/projects/esp ... _page.html
except for step 4 as I don't need OTA updates.
However - it says "After you complete the above steps, GitHub Actions will automatically trigger the compilation of your ESP-AT firmware." But it doesn't happen. Is there an extra step needed that's missing, or does this only work on non-free accounts maybe?
Any help appreciated!
Thanks...
ESP8266 Compile on Github
Re: ESP8266 Compile on Github
Hi,
1. Are you compiling under the esp-at project under your own account warehouse.
2. You can see if there is your compiled firmware on the following page under the esp-at project in your warehouse
1. Are you compiling under the esp-at project under your own account warehouse.
2. You can see if there is your compiled firmware on the following page under the esp-at project in your warehouse
Re: ESP8266 Compile on Github
If you want to compile the ESP8266 AT firmware, you need to compile it based on the release/v2.2.0.0_esp8266 branch.
Re: ESP8266 Compile on Github
Hi..
Thanks for the reply.
I followed the instruction in the espressif document exactly. so I forked the release/v2.2.0.0_esp8266 branch into my own account, as it shows to do.
The workflow page remains blank - "there are no workflow runs yet" and it only shows under my own account listing.
It looks the same as the ustccw example account in the document.
The instructions say it should compile automatically after a commit, but this doesn't happen. I assume there is perhaps a step missing in the instructions?
On the main esp-at account there seem to be only official forks.
Thanks for the reply.
I followed the instruction in the espressif document exactly. so I forked the release/v2.2.0.0_esp8266 branch into my own account, as it shows to do.
The workflow page remains blank - "there are no workflow runs yet" and it only shows under my own account listing.
It looks the same as the ustccw example account in the document.
The instructions say it should compile automatically after a commit, but this doesn't happen. I assume there is perhaps a step missing in the instructions?
On the main esp-at account there seem to be only official forks.
Who is online
Users browsing this forum: No registered users and 32 guests