[bug] Unknown revision or path not in the working tree (Vercel deployment) #1750
Assignees
Labels
bug
Something isn't working
Comments
|
@KostiantynPopovych Does vercel do a shallow checkout? We require some history to query affected files. At least in this logs, it's just +1 commit ( |
|
Hey, @milesj, thanks for a such fast reply! I want to share my experience with debugging this issue. I tried to create and deploy a repo with a fresh git history, and as a result, I got this error. Then, I created a new repo based on your example, and the original issue was still in place. As you replied, I tried to push one more commit to the example repo clone, and the problem was gone. I tried to reproduce it with another example clone, and the problem is present only if I push a single commit. The only thing I can't reproduce is the original error message, which is: So, it seems like it's not a moonrepo issue, and you could simply close this issue. |
|
It's a bit weird, since we actually query how many commits there are: https://github.com/moonrepo/moon/blob/master/crates/vcs/src/git.rs#L761 I can see this command being ran in your logs. Is this a detached checkout perhaps? I'm assuming so, and the main branch isn't actually fetched down. |
|
Hey, I'm not sure how to get an answer for your question, but I can provide at least a full log, and here I was lucky to get the original error I was mentioning - Click me |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm trying to deploy the Next.js application with an initial git commit to Vercel, and the build task fails.
Steps to reproduce
.gitfolder.git init.Expected behavior
The app should be built successfully.
Screenshots
Vercel project configuration.
Environment
Additional context
Relative portion of the logs. Could provide the entire log stream late if needed.
The text was updated successfully, but these errors were encountered: