coverallsapp / coverallsapp/github-action

Support `git` workspace directory different from `GITHUB_WORKSPACE`.

Open
#200 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 there

When I change the locating of my git working directory to not be GITHUB_WORKSPACE any more I get the following error:

Run coverallsapp/github-action@master
  with:
    github-token: ***
    base-path: pytrnsys_gui
    path-to-lcov: test-results/coverage.lcov
    coveralls-endpoint: https://coveralls.io/
    debug: false
  env:
    PYTRNSYS_DEPENDENCY_CHANGED: false
Using lcov file: test-results/coverage.lcov
Error:  "2024-03-21T10:20:50.198Z"  'error from getOptions'
Error: Error: Command failed: git cat-file -p 0d6091d8b57ef9e37bd44fb7ed8ead3b523ee6c2
fatal: Not a valid object name 0d6091d8b57ef9e37bd44fb7ed8ead3b523ee6c2

As you can see I've tried using base-path but I imagine that's not "good enough" to specify that my git working directory is somewhere else. Is there any way to change the path to the git working directory?

Thanks

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 tracing how coverallsapp/github-action resolves the git working directory and how base-path relates to GITHUB_WORKSPACE, then reproduce the failure with git checked out elsewhere. Done means the action can locate the repository and resolve git cat-file successfully while still uploading test-results/coverage.lcov.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.