Open andreasabel opened 3 years ago
Add a top level cabal.project
with packages: source/
. That is something you would do if you used cabal
for development.
Then you could use haskell-ci ... cabal.project
.
i'm not sure we want to complicated things with supporting definitions in a non-root of the repository.
Thanks! That worked.
For discoverability of the solution, could the following change to haskell-ci
make sense?
haskell-ci
is invoked with path/to/file.cabal
rather then just file.cabal
, abort with an error and suggest to create a cabal.project
file.
I suppose I should invoke
haskell-ci
in the project root folder. If the.cabal
file is a subdirectory, the GHA generation succeeds, but the generated actions fail.I tried this for my project https://github.com/BNFC/bnfc :
Here is part of the generated action script: https://github.com/BNFC/bnfc/blob/f6cb500ec755ae144d6661061ac1936acf8c5d29/.github/workflows/haskell-ci.yml#L112-L120
The action fails at
sdist
https://github.com/BNFC/bnfc/runs/1589741681?check_suite_focus=true :