codecov / codecov/codecov-action

No docs on how to point the tool at a swift coverage report

Open
#1,038 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Feature] Coverage [Product] Report Upload [Source] Open Source [Type] Docs codecov/codecov-action
Dominant language
Python
Stars
1.7k
Forks
260
Avg merge
1d 7h
Merged PRs (30d)
1

Description

The coverage reports that come out of xcodebuild are a "bundle" which is a directory containing an Info.plist and a Data directory full of binary files. I'm not entirely sure if that's what you mean to support when you say "Run with swift coverage support", but if it is, it would be good to know what file and directory options you expect to get.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the existing “Run with swift coverage support” guidance and how the action interprets its file and directory options. Confirm whether an xcodebuild bundle with Info.plist and a Data directory is supported, then document the expected inputs and an example; done when users can configure the action without guessing.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, swift
Domain
ci-cd, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.