Skip to content

Add preflight automation for Tab5 builds#170

Merged
baba-dev merged 1 commit into
mainfrom
codex/add-preflight-build-and-boot-loop-guard
Sep 20, 2025
Merged

Add preflight automation for Tab5 builds#170
baba-dev merged 1 commit into
mainfrom
codex/add-preflight-build-and-boot-loop-guard

Conversation

@baba-dev
Copy link
Copy Markdown
Owner

Summary

  • document a required preflight workflow for AI contributors and surface it in the main agent contract
  • add a repo-level preflight script plus boot-loop guard helper referenced by new contributor guidance
  • wire GitHub Actions IDF preflight workflow to run the same automation in CI

Testing

  • python -m compileall scripts/bootloop_guard.py

https://chatgpt.com/codex/tasks/task_e_68cf23f8f4ac832496701d6f07d02687

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Codex Review: Here are some suggestions.

Reply with @codex fix comments to fix any unresolved comments.

About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".

Comment thread scripts/preflight.sh
Comment on lines +7 to +16
echo "[preflight] Using repo installer to setup ESP-IDF..."
bash tools/install_idf.sh

echo "[preflight] Fetching external components..."
python ./fetch_repos.py

echo "[preflight] Building Tab5 app (esp32p4)..."
pushd platforms/tab5 >/dev/null
idf.py set-target esp32p4
idf.py build
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P1] Source IDF installer so subsequent idf.py invocations work

The preflight script runs bash tools/install_idf.sh and then immediately calls idf.py to build. Because the installer is executed in a subshell, any environment variables or PATH changes made inside it (via export.sh) are discarded when the command returns. On a fresh machine where ESP‑IDF is not already on PATH, the later idf.py set-target/idf.py build calls will fail with idf.py: command not found. The install script needs to be sourced (e.g. . tools/install_idf.sh) or refactored to emit environment variables so that idf.py is usable in the remainder of the preflight run.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@codex fix comments

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary

  • Sourced the ESP-IDF installer within the preflight script so environment setup persists for the subsequent idf.py commands. scripts/preflight.shL7-L9

Testing

  • bash -n scripts/preflight.sh

View task →

@baba-dev baba-dev merged commit c429671 into main Sep 20, 2025
1 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant