You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I intended to experiment with cross-compilation using goreleaser-cross within a container. However, I encountered an issue where goreleaser detected that the cwd is "not a git repository." I'm looking for any suggestions on why this might occur and if there's a possible workaround.
Below is the GitHub workflow snippet that only has two steps.
goreleaser release
# shell: sh -e {0}# env:# GITHUB_TOKEN: ***
• starting release...
• loading config file file=.goreleaser.yaml
• loading environment variables
• using token from "$GITHUB_TOKEN"
• getting and validating git state
⨯ release failed after 0s error=current folder is not a git repository
Error: Process completed with exit code 1.
Thanks!
The text was updated successfully, but these errors were encountered:
So basically I did this experiment based on this article which is that it's running on the GitLab registry, so I wanted to try it on the GitHub action.
Upon investigation, I discovered that the problem stemmed from the GitHub runner image, issue actions/runner-images#6775. The command git rev-parse --is-inside-work-tree was returning the error: "dubious ownership in repository at [...]".
To resolve this issue, I implemented a (temporary) workaround by adding this step (after checking out the repo):
Hello, I intended to experiment with cross-compilation using goreleaser-cross within a container. However, I encountered an issue where
goreleaser
detected that thecwd
is "not a git repository." I'm looking for any suggestions on why this might occur and if there's a possible workaround.Below is the GitHub workflow snippet that only has two steps.
Error occurred:
Thanks!
The text was updated successfully, but these errors were encountered: