wartana/WLED
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Reference Hardware Compilation section for common environments list

Browse Source 
Co-authored-by: netmindz <442066+netmindz@users.noreply.github.com>
This commit is contained in:
copilot-swe-agent[bot]
2025-10-05 15:12:07 +00:00
parent 151a974607
commit f034601512
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.github/copilot-instructions.md vendored
View File

@@ -40,7 +40,7 @@ The build has two main phases:
2. **Build at least one hardware environment**: `pio run -e esp32dev` -- Set timeout to 30+ minutes. NEVER CANCEL. 2. **Build at least one hardware environment**: `pio run -e esp32dev` -- Set timeout to 30+ minutes. NEVER CANCEL.
- Choose `esp32dev` as it's a common, representative environment - Choose `esp32dev` as it's a common, representative environment
- Alternative environments if needed: `nodemcuv2` (ESP8266) or `esp8266_2m` - See "Hardware Compilation" section above for the full list of common environments
- The build MUST complete successfully without errors - The build MUST complete successfully without errors
- If the build fails, fix the issue before proceeding - If the build fails, fix the issue before proceeding
- **DO NOT skip this step** - it validates that firmware compiles with your changes - **DO NOT skip this step** - it validates that firmware compiles with your changes
@@ -166,7 +166,7 @@ package.json # Node.js dependencies and scripts
**To ensure CI success, you MUST locally:** **To ensure CI success, you MUST locally:**
- Run `npm test` and ensure it passes - Run `npm test` and ensure it passes
- Run `pio run -e esp32dev` (or another common environment) and ensure it completes successfully - Run `pio run -e esp32dev` (or another common environment from "Hardware Compilation" section) and ensure it completes successfully
- If either fails locally, it WILL fail in CI - If either fails locally, it WILL fail in CI
**Match this workflow in your local development to ensure CI success. Do not mark work complete until you have validated builds locally.** **Match this workflow in your local development to ensure CI success. Do not mark work complete until you have validated builds locally.**