Closed rvhonorato closed 2 months ago
Coverage variation | Diff coverage |
---|---|
Report missing for 56ca74a4a0db2faed300f323b22ddaf0426ba6e0[^1] | :white_check_mark: ∅ |
Codacy will stop sending the deprecated coverage status from June 5th, 2024. Learn more [^1]: Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.
I think these checks are way too strict..I would add this action later on in the project when the production version is stable/published and the development slows down
There are no checks, it just display things over there and this is needed for FAIRness
*the checks are configured in the repository settings - none are configured right now, this PR just just sends the coverage report to codacy. If you don't want to send the coverage reports, the repository is still linked anyway to check for code quality https://app.codacy.com/gh/haddocking/haddock3/
There are no checks, it just display things over there and this is needed for FAIRness
*the checks are configured in the repository settings - none are configured right now, this PR just just sends the coverage report to codacy. If you don't want to send the coverage reports, the repository is still linked anyway to check for code quality https://app.codacy.com/gh/haddocking/haddock3/
ok, then can't it be hidden from the actions report? I really hate seeing failed actions (see https://github.com/haddocking/haddock3/pull/862) for reasons like this https://app.codacy.com/gh/haddocking/haddock3/pull-requests/862/issues#issue-da28e38929afc9695f2cd4cb38d5e415
That's a configuration in codacy, has nothing to do with this PR
This add integration with Codacy - https://app.codacy.com/gh/haddocking/haddock3/, in line with the other tools from the group