Add dependency-submission workflow to collect gradle dependencies #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Gradle Dependency Submission for cloudberry-pxf
GitHub can collect[1] gradle dependencies on its own. However It fails to collect it when
build.gradleis located in the nested directory.Adding new github-action workflow that mimics what github doing automatically[2].
[1] https://github.blog/changelog/2025-05-27-dependency-auto-submission-now-supports-gradle/
[2] https://docs.github.com/en/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/configuring-automatic-dependency-submission-for-your-repository#gradle-projects