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
I'm using vercel-action only to deploy to Vercel, while the build is done in Github Actions
- name: Checkout main repo
uses: actions/checkout@v3
with:
path: main
fetch-depth: 0
- name: Checkout UI
uses: actions/checkout@v3
with:
repository: company/some-repo
path: ui
# the rest of the steps to perform a build
- uses: amondnet/vercel-action@v19 #deploy
with:
vercel-token: ${{ secrets.VERCEL_TOKEN }}
vercel-org-id: ${{ secrets.VERCEL_ORG_ID}}
vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID}}
working-directory: main
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 having working-directory option to provide the full path of the static build?
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 zeit-token as required (although, workflow runs with no issues). This isn't the case with v25 of this action, there is no such linting issue.
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: