Switch to codecov for coverage visibility / validation

Open
#159 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, java
Domain
ci-cd, testing-qa

Research direction

Start by inspecting the GitHub Actions workflow that publishes coverage and the current coverage badge configuration; the issue links to a failing workflow run. Confirm how coverage is currently generated and what permissions cause the failure. Done means coverage is published and validated through Codecov, with the repository's coverage visibility updated accordingly.

Written by the indexing model from the issue text.

Description

Currently the workflow to publish the code coverage results is failing due to github permissions (e.g. https://github.com/Flagsmith/flagsmith-java-client/actions/runs/10142818065/job/28042881519). For now, I'm going to remove the code coverage badge, and in the future, we'll move to codecov.io.

Dominant language
Java
Stars
28
Forks
22
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Flagsmith/flagsmith-java-client

All issues in Flagsmith/flagsmith-java-client

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.