Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coverage fails on tagged release "No commit for SHA ..." #18

Open
borislemke opened this issue Feb 26, 2021 · 1 comment
Open

Coverage fails on tagged release "No commit for SHA ..." #18

borislemke opened this issue Feb 26, 2021 · 1 comment

Comments

@borislemke
Copy link

When running coverage report action on a tagged release, we get an error with following details:

RequestError [HttpError]: No commit found for SHA: xxxxxxxx
    at /home/runner/work/_actions/romeovs/lcov-reporter-action/v0.2.19/dist/main.js:6018:23
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async main$1 (/home/runner/work/_actions/romeovs/lcov-reporter-action/v0.2.19/dist/main.js:22998:3) {
  name: 'HttpError',
  status: 422,

This works fine for the main branch though. I reckon this might not be specific to this GitHub Action and something else, but wanted to share this here in case anybody has stumbled upon the same and found a solution.

Screen Shot 2021-02-26 at 16 08 54

@ShaMan123
Copy link

ShaMan123 commented Oct 1, 2022

This horrible thing took a lot of my time.
I've experienced it in a different workflow.
Make sure you checkout to a branch, since tags checkout to a commit, whatever that means.
target_commitish in event context - VERY POORLY documented

- uses: actions/checkout@v3
  with:
     ref: ${{github.event.release.target_commitish}}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants