Skip to content

Check conventions formatting in CI#19295

Open
trask wants to merge 2 commits into
open-telemetry:mainfrom
trask:ci/check-conventions-spotless
Open

Check conventions formatting in CI#19295
trask wants to merge 2 commits into
open-telemetry:mainfrom
trask:ci/check-conventions-spotless

Conversation

@trask

@trask trask commented Jul 22, 2026

Copy link
Copy Markdown
Member

The root spotlessCheck task does not check the conventions directory because it is a separate included Gradle build. As a result, formatting violations in convention plugins are currently not caught by CI.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds CI formatting validation for the separate conventions Gradle build and applies required formatting fixes.

Changes:

  • Runs spotlessCheck for the conventions build.
  • Applies Spotless formatting without behavioral changes.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.

Show a summary per file
File Description
.github/workflows/build-common.yml Checks conventions formatting in CI.
conventions/src/main/kotlin/otel.resolve-latest-dep-versions.gradle.kts Applies Kotlin formatting.
conventions/src/main/kotlin/otel.java-conventions.gradle.kts Applies naming and formatting fixes.
conventions/src/main/kotlin/otel.japicmp-conventions.gradle.kts Corrects indentation.
conventions/src/main/kotlin/io.opentelemetry.instrumentation.base.gradle.kts Applies comment and interpolation formatting.

@trask
trask marked this pull request as ready for review July 22, 2026 17:07
@trask
trask requested a review from a team as a code owner July 22, 2026 17:07
@opentelemetry-pr-dashboard

opentelemetry-pr-dashboard Bot commented Jul 22, 2026

Copy link
Copy Markdown

Pull request dashboard status

Status last refreshed: 2026-07-24 10:58:57 UTC.

  • Waiting on: Maintainers
  • Next step: Merge when ready.

This automated status or its linked feedback items may be incorrect. If something looks wrong, please report it with the result you expected.

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.

3 participants