The GitHub Actions job "Required Checks" on texera.git/main has succeeded. Run started by GitHub user github-merge-queue[bot] (triggered by github-merge-queue[bot]).
Head commit for run: 2c2b76b9ea8a0935aca6f798d35ad15baba26853 / Yicong Huang <[email protected]> docs(local-dev): fix stale comment claiming infra is unmanaged (#6025) ### What changes were proposed in this PR? The usage banner in `bin/local-dev/main.sh` claimed Docker infra is **not** managed by the script and that you must bring it up yourself before `up`. That contradicts the actual code: `cmd_up` calls `infra_up` (which runs `docker compose up -d` against project `texera-local-dev`) and `cmd_down` calls `infra_down` for any docker targets. ``` Before: comment says "infra is NOT managed here -- bring those up yourself" After: comment says "infra IS managed: `up` brings it up, `down` tears it down" ``` Comment-only change; no behavior change. ### Any related issues, documentation, discussions? Related to #5960 (introduced `bin/local-dev` and this banner) and #6007 (wired `infra_up` into `up`/`auto`, which is what made the banner stale). No dedicated issue — documentation/comment-only fix (issue-first is excepted for docs). The sibling `bin/local-dev/README.md` already documents the correct behavior ("infra in docker, JVM + frontend native"); this just realigns the script's own banner. ### How was this PR tested? No tests — comment-only change. Verified the described behavior by reading `cmd_up` → `infra_up` (`docker compose up -d`, project `texera-local-dev`) and `cmd_down` → `infra_down`, and by running `bin/local-dev.sh up`, which brought up postgres/minio/lakefs/lakekeeper/litellm automatically (14/14 services healthy) with no manual `docker compose` step. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.8) Report URL: https://github.com/apache/texera/actions/runs/28410990439 With regards, GitHub Actions via GitBox
