-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
.git not found when using working-directory #149
Comments
@wmcheung Try this. uses: amondnet/vercel-action@e610ddb0e844d1a22c4b27560c224f84f20f3061
with:
working-directory: your-working-dir
git-directory: your-git-dir
|
I had the same issue, and running this action off that commit works well. However, this is a nit, I am using VSCode with github extension and apparently it lints actions and I can see that this commit marks |
Will this be fixed? I am experiencing the same issue |
Same issue here |
I'm using vercel-action only to deploy to Vercel, while the build is done in Github Actions
What I've encountered is that the working-directory is called after running a
git log
. Which means that deploy is not happening inside the working-directory. Vercel action will try to look for history using git in the root where no.git
is available.My current workaround is to have the main repo without a path. But for multi checkout purpose I think the index.js file should be updated to have a
path
option to tell vercel-action where the root of the project is? While havingworking-directory
option to provide the full path of the static build?vercel-action/index.js
Line 360 in f445edf
vercel-action/index.js
Lines 114 to 116 in f445edf
The text was updated successfully, but these errors were encountered: