Skip to content
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

Error: Unable to Get Current Branch Name When Committing with Evergit #8

Open
IanSkelskey opened this issue Nov 29, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@IanSkelskey
Copy link
Owner

When attempting to commit changes using evergit commit in a local repository, the command fails with the error message:

? Select files to stage:  .gitignore,  README.md,  something.py
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
C:\Users\iansk\AppData\Roaming\nvm\v20.18.0\node_modules\evergit\dist\util\git.js:137
        throw new Error('Unable to get current branch name.');
              ^

Error: Unable to get current branch name.
    at getCurrentBranchName (C:\Users\iansk\AppData\Roaming\nvm\v20.18.0\node_modules\evergit\dist\util\git.js:137:15)
    at C:\Users\iansk\AppData\Roaming\nvm\v20.18.0\node_modules\evergit\dist\cmd\commit.js:41:55
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\iansk\AppData\Roaming\nvm\v20.18.0\node_modules\evergit\dist\cmd\commit.js:5:58)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Node.js v20.18.0
@IanSkelskey IanSkelskey added the bug Something isn't working label Nov 29, 2024
@IanSkelskey
Copy link
Owner Author

This also happened when I cloned an empty repo and tried to use evergit for the first commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant