Skip to content

[FLINK-40181][ci] Make spotless checking changes since last green build in ci#28776

Open
snuyanzin wants to merge 1 commit into
apache:masterfrom
snuyanzin:flink40181
Open

[FLINK-40181][ci] Make spotless checking changes since last green build in ci#28776
snuyanzin wants to merge 1 commit into
apache:masterfrom
snuyanzin:flink40181

Conversation

@snuyanzin

Copy link
Copy Markdown
Contributor

What is the purpose of the change

The PR makes GHA running spotless against files changed since last successful build rather than for everything
also more details are at diffplug/spotless#511

Brief change log

GHA: check for last green branch and make spotless running for changes since that branch

Verifying this change

GHA

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): ( no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): (no)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
  • The S3 file system connector: (no)

Documentation

  • Does this pull request introduce a new feature? ( no)
  • If yes, how is the feature documented? (not applicable)

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

@flinkbot

flinkbot commented Jul 19, 2026

Copy link
Copy Markdown
Collaborator

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

@snuyanzin

Copy link
Copy Markdown
Contributor Author

example of GHA https://github.com/snuyanzin/flink/actions/runs/29693623019
from my fork

@snuyanzin

Copy link
Copy Markdown
Contributor Author

@flinkbot run azure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants