You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* test: add tests for all remaining tools
Problem: most formatters and linters in guard-collection had no test
coverage. The csharpier binary was renamed in v1.0+ and ruff's -e flag
was deprecated in favor of the check subcommand.
Solution: add 42 test files covering every remaining tool, fix the
csharpier and ruff definitions, extend the install script with gz/jar
archive types, add 6 new CI jobs (dotnet, ruby, clojure, elixir, nix,
swift), and expand existing jobs with newly tested tools.
* fix(ci): remove duplicate entry and untestable mypyc test
* fix(ci): restore CI config lost during merge
Problem: the -X theirs merge strategy replaced the full test/all-tools
CI config with the smaller fix/broken-configs version, losing install
entries for dart, fish_indent, google-java-format, pg_format, tombi,
typos, typstyle, xmllint, and zigfmt.
Solution: restore binary.txt, ci.yaml, and install script from the
pre-merge test/all-tools state which already had all entries.
* ci: extract repeated test setup into composite action
Problem: every test job repeated the same 5 steps for neovim, lua,
luarocks, busted/nlua, and guard.nvim clone — 175 lines of duplication
across 15 jobs.
Solution: extract into .github/actions/test-setup/action.yml and
replace with a single `uses: ./.github/actions/test-setup` per job.
* fix(test): use run_lint/run_fmt instead of manual vim.system
Problem: rebase picked up old test versions that manually construct
commands instead of using the config-driven helpers, defeating the
purpose of testing the actual tool definitions.
Solution: replace all 14 affected test files with the upstream/main
versions that use run_lint/run_fmt. Add buf lint test using run_lint.
* ci(cljfmt): use standalone binary and extract apt packages to file
Problem: cljfmt required a dedicated CI job with Java, Clojure CLI, a
hand-rolled wrapper script, and dep pre-warming. The binary job also had
an inline apt-get install command inconsistent with other tool lists.
Solution: switch cljfmt to the standalone GraalVM binary from GitHub
releases, move its test into test/binary/, delete the test-clojure job,
and extract the binary job's apt packages into binary-apt.txt.
* ci: retrigger
* ci: retrigger
* ci: re-trigger
* fix(rubocop): use rubocop directly instead of bundle exec
Problem: rubocop formatter and linter definitions used
`bundle exec rubocop`, requiring a Gemfile and bundle install
in both tests and CI.
Solution: invoke rubocop directly via `gem install rubocop`.
Remove Gemfile setup from test and CI.
0 commit comments