coverallsapp / coverallsapp/github-action

Coveralls won't comment or set status on PR if repository has not yet been configured

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

Nobody has claimed this yet.

Dominant language
No language data
Stars
520
Forks
78
PR merge metrics
No merged PRs in 30d

Description

Hi all,

I just ran into an issue where Coveralls won't add comments or set the pull request status on a brand new repository.

To reproduce this issue, create a public Github repository, push some code to it, create a PR, push some trivial changes to it, then run this action without first adding the repository on https://coveralls.io.

Coveralls will gather coverage just fine, but won't update the pull request.

I have added a demonstration of this at https://github.com/ThePadawan/coveralls-action-demo/pull/1 .

The issue can be solved by adding yourself as the repository owner on https://coveralls.io, but this is currently not mentioned anywhere.

I have linked a PR that adds a troubleshooting section for this. I would be glad if you could merge it (after moving the static image asset!) to save other users the same trouble I had debugging this issue.

Cheers!

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

Review the existing project documentation and the linked demonstration PR to understand where the troubleshooting guidance belongs. Add a troubleshooting section explaining that new repositories must first be added by their owner on Coveralls, and move the static image asset as noted; the documentation should cover the setup needed for comments and pull-request status updates.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.