bazel-contrib / bazel-contrib/rules_scala

Add Skylint checks to CI

Open
#336 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Starlark
Stars
384
Forks
292
Avg merge
2d 21h
Merged PRs (30d)
46

Description

It would be helpful to avoid deprecation surprises and maintain code quality to run [Skylint](https://github.com/bazelbuild/bazel/blob/master/site/docs/skylark/skylint.md) on `rules_scala` in CI.

Right now we have [39 warnings](https://github.com/bazelbuild/rules_scala/files/1465260/skylint.txt) that we would need to address before doing so. Should we make tickets for each group of warnings? Or work on them all in this issue?

Contributor guide

Open the contributing guide

Research direction

Begin with the attached skylint.txt warning list and the linked Skylint documentation. Group the 39 warnings, then inspect the repository's CI configuration to determine where the check belongs. Done means the warnings are addressed and Skylint runs successfully in CI.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, ci-cd, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.