Skip to content

ci: lint: enable linting also for manual targets - #593

Open
fbaeuerle wants to merge 2 commits into
mainfrom
fb/541/manual_targets
Open

fbaeuerle wants to merge 2 commits into
mainfrom
fb/541/manual_targets

Conversation

@fbaeuerle

Copy link
Copy Markdown
Contributor

Also targets that are tagged manual are worthy of linting. Ensure they are linted without breaking the build.

Closes: #541

Deeply-nested Bazel target paths flattened into a filename can exceed
the filesystem's 255-byte limit and crash clean_lint_sarif.py. The
merge step only globs for "*.sarif", so a hash is enough to keep names
unique.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview for this pull request is available at:
pr-593: https://eclipse-score.github.io/baselibs/pr-593/

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 Changes recommended

The non-blocking manual-target step can silently skip lint coverage when discovery or lint execution fails.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

Adds lint coverage for compatible Bazel targets tagged manual.

Changes:

  • Discovers compatible manual C++, Rust, and Python targets.
  • Runs linters separately for those targets.
  • Hashes SARIF filenames to avoid filesystem limits.
File summaries
File Description
.github/workflows/lint.yml Adds manual-target linting.
.github/tools/manual_lint_targets.sh Finds compatible lintable manual targets.
.github/tools/clean_lint_sarif.py Uses hashed SARIF filenames.
Review details
  • Files reviewed: 3/3 changed files
  • Comments generated: 1
  • Review effort level: Balanced

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread .github/workflows/lint.yml Outdated
Bazel excludes manual targets from //..., so rules_lint aspects never
see them. Build them explicitly by name in a separate, non-blocking
step so clang-tidy/Clippy/Ruff still catch issues in them.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@fbaeuerle
fbaeuerle force-pushed the fb/541/manual_targets branch from 92125d3 to 46cf5d7 Compare September 17, 2026 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci CI related changes

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

ci: consolidate C++, Rust, and Python linting with rules_lint

2 participants