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
Following the getting started, when running the yarn best command the CLI throws the following error:
ERROR Error: Unable to read git information
at generateProjectConfigs (/Users/p.dartus/code/github/pmdartus/benchmark-ci-test/node_modules/@best/config/build/index.js:10:19)
at readConfig (/Users/p.dartus/code/github/pmdartus/benchmark-ci-test/node_modules/@best/config/build/index.js:68:45)
at process._tickCallback (internal/process/next_tick.js:68:7)
error Command failed with exit code 1.
Does best should absolutely require to be run in a git enabled directory? If it is the case then the documentation needs to be updated.
Update:
I took me multiple attempts to make the best CLI happy:
after running git init, best requires at least 1 commit on the master branch.
after running git commit, best requires at least a remote to be present.
That’s a good question. I believe there are a good number of things that assume the Git info will be available, but that should be reasonably easy to fix since we have types!
What do you think @diervo, should we require users to run Best in a git enabled directory?
Observations
Following the getting started, when running the
yarn best
command the CLI throws the following error:Does best should absolutely require to be run in a git enabled directory? If it is the case then the documentation needs to be updated.
Update:
I took me multiple attempts to make the best CLI happy:
git init
, best requires at least 1 commit on the master branch.git commit
, best requires at least a remote to be present.Versions
10.16.0
4.0.0-alpha4
The text was updated successfully, but these errors were encountered: