aglinxinyuan commented on PR #5364: URL: https://github.com/apache/texera/pull/5364#issuecomment-4637830158
Confirmed — it doesn't. The file is `amber/system-requirements-lock.txt`, and the `pyamber`/`dependencies` globs are `**/requirements.txt` + `**/*-requirements.txt` — the lockfile matches neither (it ends in `-lock.txt`), so the PR got no `pyamber` label → empty stack union in required-checks → all build stacks skipped. (The green checks here are from the post-merge push to `main`, which runs every stack unconditionally — not PR validation.) Fixed in #5399: a single `**/*requirements*.txt` glob in both sections, covering `requirements.txt`, `*-requirements.txt`, and `system-requirements-lock.txt`. Verified against the repo — those four `amber/` manifests are the only `*requirements*.txt` files, so it can't widen scope: ``` amber/system-requirements-lock.txt => pyamber, dependencies (was: none) amber/requirements.txt => pyamber, dependencies (unchanged) frontend/package.json => frontend, dependencies (unchanged) ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
