Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[CI] Core CI doesn't run for changes to amoro-format-lance (and amoro-web)

Open Beginner friendly
  • Is something wrong?
#4,417 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@MarkAlex1234 is already working on this.

Since Oct 5, 2026.

  • #4418 by @MarkAlex1234 — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, yaml
Domain
ci-cd

Research direction

Read core-hadoop2-ci.yml and core-hadoop3-ci.yml, focusing on their pull_request.paths lists. Add the amoro-format-lance/** path to both lists, then verify that changes under that module trigger the core CI workflows.

Written by the indexing model from the issue text.

Description

What happens

core-hadoop2-ci.yml and core-hadoop3-ci.yml build and test the whole reactor (./mvnw clean install ...), but on pull requests they only trigger on an explicit module list: amoro-ams, amoro-common, amoro-metrics, amoro-optimizer, amoro-format-{iceberg,paimon,hudi} and three amoro-format-mixed submodules. amoro-format-lance was added to the root pom.xml modules later and isn't in either list, and no other workflow mentions it.

amoro-ams/pom.xml depends on amoro-format-lance (test scope, plus compile scope in two profiles). So a PR that only changes amoro-format-lance/** runs no CI at all, neither lance's own tests nor the AMS tests that use it, and breakage only shows up on the next PR that touches a listed module.

amoro-web is in the same position: amoro-ams depends on the amoro-web artifact, but no workflow watches amoro-web/**. That may be intentional, since frontend-only changes would otherwise run the full core matrix, so I'm only flagging it.

Proposed fix

Add "amoro-format-lance/**" to the pull_request.paths of core-hadoop2-ci.yml and core-hadoop3-ci.yml. I have a two-line PR ready and will link it here.

(Found by comparing each workflow's paths: with the Maven module graph using npx github:Continuous-Actions/dynamic-monorepo audit. Disclosure: that's a GitHub Action I maintain. The fix itself is just the path entry.)

Dominant language
Java
Stars
1.2k
Forks
398
Avg merge
1d 14h
Merged PRs (30d)
19

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/amoro

All issues in apache/amoro

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.