Remove qlty integration from CI - #284
Merged
Merged
Conversation
The br_danfe project on Qlty Cloud is paused, so `qlty coverage publish` hard-fails CI (HTTP 400) even when the test suite passes. facil123 already dropped qlty in favor of couve for the same reason (no one was consuming the qlty.sh dashboard). Reverts the CI/coverage-formatter changes from Setup Qlty (#254) and its follow-up (#255). Refs #283 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resumo
curl https://qlty.sh | sh+qlty coverage publish) do jobrspecem.github/workflows/config.yml.spec/spec_helper.rbpara gerar cobertura só em HTML (o formatter JSON só existia para alimentar oqlty coverage publish).simplecov-json, agora sem uso.Por quê
O projeto
br_danfeno Qlty Cloud está pausado, eqlty coverage publishtrata "paused project" como erro fatal (HTTP 400), quebrando o CI mesmo com a suíte passando 100%. Confirmado ao rerodar as PRs #280 e #281: ambas com testes verdes, falhando só nesse step.O
facil123já tinha cortado o qlty pelo mesmo motivo (redundante com ocouve, que já fazia o gate de cobertura + comentário na PR).Fecha #283.
Plano de teste
bundle exec rspeclocal: 291 examples, 0 failuresbundle exec rubocop --display-cop-names --parallellocal: sem ofensas🤖 Generated with Claude Code