when running dotnet neoxp checkpoint create checkpoints/contracts-deployed -f it actually reads the neo express default file from a temporary file on the computer, and not relative to where the command is run. this can be bypassed locally by adding -i default.neo-express.
but when running this into github actions, we can not specify it, thus making github actions brokens for this particular command.
Note: if we pass an absolute path, it works as intended, the issue is only specific to relative paths. (obviously we can not use absolute paths for github actions)
Jim8y
commented
3 weeks ago
there is still an issue with relative path on neo express.
There was an attempt to fix it it seems but it still does not work as intended, and while it was working for a long time it is not anymore: https://github.com/neo-project/neo-express/pull/438
Issue:
when running
dotnet neoxp checkpoint create checkpoints/contracts-deployed -fit actually reads the neo express default file from a temporary file on the computer, and not relative to where the command is run. this can be bypassed locally by adding-i default.neo-express.but when running this into github actions, we can not specify it, thus making github actions brokens for this particular command.
Note: if we pass an absolute path, it works as intended, the issue is only specific to relative paths. (obviously we can not use absolute paths for github actions)