coverallsapp / coverallsapp/github-action
Coverage isn't published within parallel builds
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 520
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I am trying to configure coveralls with parallels builds using GitHub Actions with your documentation: https://docs.coveralls.io/parallel-build-webhook
So, As I understand by coverage isn't published due my builds is in pending state (waiting for web hook?)
I've added at last step (finish section) I just call curl with my repo token, and it's returned 404 error, how to configure it properly and could you please add such steps into your documentation
finish:
needs: build
runs-on: ubuntu-latest
steps:
- name: Coveralls finished
run: |
curl https://coveralls.io/webhook?repo_token=${{ secrets.coveralls }}
Example: https://github.com/pbelskiy/aiojenkins/actions/runs/106594356
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the parallel-build webhook documentation at docs.coveralls.io/parallel-build-webhook and compare it with the provided GitHub Actions workflow and linked action run. Clarify the correct finish-step configuration and document the steps needed to publish coverage without a 404 response.
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
- Mostly clear
- Newbie friendliness
- 35/100