Fixed: The coverage status checks on a commit could report a different number than the coverage comment on the same pull request. A status was built from a single coverage report, while the comment uses the whole commit. So if you upload more than one flag or component per commit, or you use carry-forward, the status measured only part of your coverage but compared it against a complete base. For repositories that upload one flag per commit and carry the rest forward, this made the Coverage Change check fail on almost every pull request, whatever the pull request contained. Both now report the same number. We also write the status again as each upload arrives, so a commit built from several uploads settles on the complete figure.
Fixed: Patch coverage counted changed lines borrowed from your default branch. Carry-forward fills in the flags and components a commit did not upload, and those reports describe a different set of changes. Their changed lines were added to yours, so a pull request that changed 10 lines could be reported as changing several hundred, at a much lower percentage. Patch coverage now counts only the lines the commit itself changed, in the pull request comment, the status check and the dashboard. Overall coverage still includes carried-forward coverage, which is what the feature is for. Our earlier note said the Patch figure stayed reliable when carry-forward is enabled — that was not true, and it is now.
Fixed: The Coverage Change status check compared against the newest commit on your base branch, while the pull request comment compared against the commit your pull request is based on. When the base branch moved ahead, the two reported different changes for the same commit. Both now use the same commit: your pull request base when it has coverage, and the base branch when it does not — the comment already tells you when that happens.
We regularly update our changelog in an effort to improve transparency into the development process. If you have any questions or feedback, please don't hesitate to contact us.
If you are a user of OtterWise already, or have been reading our blog, you might already know that we take privacy extremely serious, even when it comes to protecting your code as if it was sensitive personal information, this goes for everything we do, which is why we publish changelogs for even smaller updates, rather than just major releases.
Our weekly digest for OtterWise users also includes our changelog in the bottom (see related changelog), to keep you up-to-date with the latest changes.
PR comments, status checks, line annotations, and trends, all without code access. Free for public repos; per-repo pricing for private repos.
