coverallsapp / coverallsapp/github-action

Always getting Error: Bad response: 422 {"message":"Couldn't find a repository matching this job.","error":true}

Open
#81 3 comments 2 reactions 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

Trying to use a private repo with the github action using the following .yml:

on: ["push", "pull_request"]

name: Test Coveralls

jobs:

  build:
    name: Build
    runs-on: ubuntu-latest
    steps:

    - uses: actions/checkout@v1

    - name: Use Node.js 10.x
      uses: actions/setup-node@v1
      with:
        node-version: 10.x

    - name: npm install, npm test -- --coverage
      run: |
        npm install
        npm test -- --coverage

    - name: Coveralls
      uses: coverallsapp/github-action@master
      with:
        github-token: ${{ secrets.GITHUB_TOKEN }}

this is the exact same .yml provided on https://github.com/coverallsapp/github-action as the "standard example" with make test-coverage swapped for npm test -- --coverage (to generate lcov.info).

I've logged into the website and turned the repository "on" and I see the repository in the "my repos" tab, but still the action always fails with the following:

Screen Shot 2021-05-06 at 3 12 39 AM

I'm kind of stumped, are there some better docs to take a look at or any working examples?

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 with the workflow YAML and the coverallsapp/github-action@master step, then inspect how GITHUB_TOKEN and private repositories are handled. Reproduce the failure with the provided workflow and lcov.info, and compare it with the action documentation or working examples. Done means the action can locate the private repository and submit coverage successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.