docs: fix stale core/ directory paths in contribution docs by Yicong-Huang · Pull Request #6111 · apache/texera

Yicong-Huang · 2026-07-04T18:02:19Z

What changes were proposed in this PR?

Docs still referenced the pre-ASF core/ source tree. This PR updates every such path to the current layout:

Stale	Current
`core/workflow-operator/.../edu/uci/ics/amber/operator`	`common/workflow-operator/.../org/apache/texera/amber/operator`
`core/gui`, `/core/new-gui` (operator images)	`frontend/src/assets/operator_images`
`cd core` / `cd core/gui` (test instructions)	repo root / `cd frontend`
`config/src/main/resources/...`	`common/config/src/main/resources/...`
`core/amber/.../generator_operator.py` (renamed)	`amber/.../generator_operator_integer.py`

Also removes docs/contribution-guidelines/micro-services-local-dev.md: it documents the now-finished core/micro-services migration and build scripts that no longer exist; local development is covered by the developer guide and bin/local-dev.sh. No other doc links to that page.

Any related issues, documentation, discussions?

Closes #6105

How was this PR tested?

Docs-only change. Every new path/link target was verified to exist in the repo:

ls common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/{regex,huggingFace,map,filter,flatmap,aggregate}
ls frontend/src/assets/operator_images
ls amber/src/main/python/pytexera/udf/examples/generator_operator_integer.py
grep -rn "core/" docs/contribution-guidelines docs/tutorials   # no stale hits remain

Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Claude Fable 5)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

github-actions · 2026-07-04T18:02:34Z

Automated Reviewer Suggestions

Based on the git blame history of the changed files, we recommend the following reviewers:

Contributors with relevant context: @Ma77Ball
You can notify them by mentioning @Ma77Ball in a comment.

Yicong-Huang · 2026-07-04T18:18:06Z

cc @Ma77Ball for review

Ma77Ball

Overall LGTM! The doc changes look reasonable and correct.

xuang7

LGTM!

### What changes were proposed in this PR? Cleans up leftovers from before the ASF migration, plus two small adjacent doc fixes: - `github.com/Texera/texera` → `github.com/apache/texera` in `CONTRIBUTING.md` (fork + Actions links), `docs/contribution-guidelines/_index.md`, `docs/examples/_index.md`, and the clone URL in `guide-for-developers.md`. - `CONTRIBUTING.md`: PRs are squash-merged into `main`, not `master` (two mentions). - `docs/examples/_index.md`: dropped the dead link to an `examples/` directory that has never existed in this repo. - `SECURITY.md`: "Kubernates PODs" → "Kubernetes pods". ### Any related issues, documentation, discussions? Closes #6107 ### How was this PR tested? Docs-only change. Verified `main` is the default branch and `apache/texera` the canonical repo (`git remote -v`, `.github/workflows/required-checks.yml`), and that `grep -rn "github.com/Texera/texera"` finds no remaining hits outside files handled by #6111. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Fable 5) --------- (backported from commit f787472) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

### What changes were proposed in this PR? Docs still referenced the pre-ASF `core/` source tree. This PR updates every such path to the current layout: | Stale | Current | | --- | --- | | `core/workflow-operator/.../edu/uci/ics/amber/operator` | `common/workflow-operator/.../org/apache/texera/amber/operator` | | `core/gui`, `/core/new-gui` (operator images) | `frontend/src/assets/operator_images` | | `cd core` / `cd core/gui` (test instructions) | repo root / `cd frontend` | | `config/src/main/resources/...` | `common/config/src/main/resources/...` | | `core/amber/.../generator_operator.py` (renamed) | `amber/.../generator_operator_integer.py` | Also removes `docs/contribution-guidelines/micro-services-local-dev.md`: it documents the now-finished `core/micro-services` migration and build scripts that no longer exist; local development is covered by the developer guide and `bin/local-dev.sh`. No other doc links to that page. ### Any related issues, documentation, discussions? Closes #6105 ### How was this PR tested? Docs-only change. Every new path/link target was verified to exist in the repo: ``` ls common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/{regex,huggingFace,map,filter,flatmap,aggregate} ls frontend/src/assets/operator_images ls amber/src/main/python/pytexera/udf/examples/generator_operator_integer.py grep -rn "core/" docs/contribution-guidelines docs/tutorials # no stale hits remain ``` ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Fable 5) (backported from commit 6829fae) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Yicong-Huang · 2026-07-04T23:49:28Z

Backport to release/v1.2 succeeded as a4dc934. Done manually — the automated backport skipped this PR because its merge commit shared a push with #6112 (see #6119, fix in #6120).

### What changes were proposed in this PR? Cleans up leftovers from before the ASF migration, plus two small adjacent doc fixes: - `github.com/Texera/texera` → `github.com/apache/texera` in `CONTRIBUTING.md` (fork + Actions links), `docs/contribution-guidelines/_index.md`, `docs/examples/_index.md`, and the clone URL in `guide-for-developers.md`. - `CONTRIBUTING.md`: PRs are squash-merged into `main`, not `master` (two mentions). - `docs/examples/_index.md`: dropped the dead link to an `examples/` directory that has never existed in this repo. - `SECURITY.md`: "Kubernates PODs" → "Kubernetes pods". ### Any related issues, documentation, discussions? Closes apache#6107 ### How was this PR tested? Docs-only change. Verified `main` is the default branch and `apache/texera` the canonical repo (`git remote -v`, `.github/workflows/required-checks.yml`), and that `grep -rn "github.com/Texera/texera"` finds no remaining hits outside files handled by apache#6111. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Fable 5) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…he head (apache#6120) ### What changes were proposed in this PR? `direct-backport-push.yml` resolved exactly one PR per push event — from `head_commit.message`, falling back to `commits/{context.sha}/pulls`. When several auto-merges land on `main` in a single ref update, only the head commit was examined and the `release/*` labels on every other PR in the same push were silently dropped: no run, no commit status, no failure comment. An audit of 2026-06-01 → 2026-07-04 found 2 of 43 labeled PRs lost this way (apache#5802, coalesced behind apache#5812; and apache#6111, coalesced behind apache#6112). Changes to the `discover` job: - Enumerate **all** commits in the push via `compareCommits(payload.before...context.sha)` (oldest first), falling back to the head commit if the compare fails or `before` is unavailable. - Resolve a PR per commit (same two strategies as before: `(#N)` title suffix, then `commits/{sha}/pulls` with backoff) and collect green `release/*` targets per PR. - Output one matrix entry per `(pr_number, merge_sha, target)` pair instead of a single PR + target list. Changes to the `push-backports` job: - Matrix is now `include: <entries>` with `max-parallel: 1`, so cherry-picks apply in commit order and two legs never race pushes to the same release branch. - `MERGE_SHA`/`PR_NUMBER` come from the matrix entry instead of `github.sha`/a single discover output; the cherry-pick, commit statuses, and PR comments all annotate the right commit and PR. - Job legs are named `backport #<pr> to <target>`; the failure-annotation job-URL matcher was updated accordingly. ### Any related issues, documentation, discussions? Closes apache#6119 ### How was this PR tested? - YAML parses (PyYAML) and all three embedded `github-script` blocks pass `node --check`. - Dry-ran the new discover logic (read-only API calls) against the two historical coalesced pushes: the 2026-07-04 push (`5c4a963f7...9cd8acf`) yields entries for **both** apache#6111 and apache#6112 with green targets, and the 2026-06-20 push range yields apache#5802 while correctly skipping the unlabeled apache#5809/apache#5811/apache#5812. The old logic produced only the head PR in each case. - Note: this fix is not retroactive — apache#5802 and apache#6111 still need manual backporting to `release/v1.2`. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Fable 5) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

docs: fix stale core/ directory paths in contribution docs

f596e1f

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

github-actions Bot assigned Yicong-Huang Jul 4, 2026

github-actions Bot added the docs Changes related to documentations label Jul 4, 2026

Yicong-Huang mentioned this pull request Jul 4, 2026

docs: fix stale repo, branch, and architecture references #6113

Merged

Yicong-Huang requested a review from chenlica July 4, 2026 18:17

Ma77Ball approved these changes Jul 4, 2026

View reviewed changes

Yicong-Huang added the release/v1.2 back porting to release/v1.2 label Jul 4, 2026

Yicong-Huang requested a review from xuang7 July 4, 2026 20:13

xuang7 approved these changes Jul 4, 2026

View reviewed changes

Yicong-Huang added this pull request to the merge queue Jul 4, 2026

Merged via the queue into apache:main with commit 6829fae Jul 4, 2026
38 checks passed

Yicong-Huang deleted the docs/core-paths branch July 4, 2026 22:59

This was referenced Jul 4, 2026

Direct backport only processes the head commit of a multi-commit push, silently skipping other labeled PRs #6119

Closed

fix(ci): backport every labeled PR in a multi-commit push, not just the head #6120

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

docs: fix stale core/ directory paths in contribution docs#6111

docs: fix stale core/ directory paths in contribution docs#6111
Yicong-Huang merged 1 commit into
apache:mainfrom
Yicong-Huang:docs/core-paths

Yicong-Huang commented Jul 4, 2026

Uh oh!

github-actions Bot commented Jul 4, 2026

Uh oh!

Yicong-Huang commented Jul 4, 2026

Uh oh!

Ma77Ball left a comment

Uh oh!

xuang7 left a comment

Uh oh!

Uh oh!

Yicong-Huang commented Jul 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

Yicong-Huang commented Jul 4, 2026

What changes were proposed in this PR?

Any related issues, documentation, discussions?

How was this PR tested?

Was this PR authored or co-authored using generative AI tooling?

Uh oh!

github-actions Bot commented Jul 4, 2026

Automated Reviewer Suggestions

Uh oh!

Yicong-Huang commented Jul 4, 2026

Uh oh!

Ma77Ball left a comment

Choose a reason for hiding this comment

Uh oh!

xuang7 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Yicong-Huang commented Jul 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants