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
A common pattern in production environments is to put a bare git repository (see repo/) outside the working directories (see releases/) so you can deploy with minimal disruption of the live release:
current -> symlink to releases/3
repo/
releases/1/
releases/2/
releases/3/
releases/3/package.json
releases/3/node_modules
releases/3/config/environment.js
import{Git}from"@nice-labs/git-rev";import*aspathfrom"path";constgit=newGit(path.relative(process.cwd(),"../../repo"))git.commitHash()// equivalent form: git rev-parse HEAD// working directory: path.relative(process.cwd(), "../../repo")
Can come and use my brand new implementation.
janwerkhoven
changed the title
"[git-rev-sync] no git repository found" when working directory is not git directory
"[git-rev-sync] no git repository found" when working with git --work-treeFeb 18, 2020
A common pattern in production environments is to put a bare git repository (see
repo/
) outside the working directories (seereleases/
) so you can deploy with minimal disruption of the live release:Which deploys with a command like:
Running
git.short()
in theenvironment.js
I keep getting this error:I tried:
Whatever I try, can't seem to grab the git repository.
Any ideas?
The text was updated successfully, but these errors were encountered: