di-sukharev / di-sukharev/opencommit
[Bug]: oco hook set is blocking vscode integrated source control
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Opencommit Version
latest
Node Version
20
NPM Version
latest
What OS are you seeing the problem on?
No response
What happened?
i installed the oco hook and my vscode (latest -v) stopped working
Expected Behavior
vscode integrated source control works fine together with oco hook
Current Behavior
it fails.
Possible Solution
No response
Steps to Reproduce
try do this:
- oco hook set
- commit smth in vscode integrated terminal
- get the
2024-10-16 10:26:16.610 [info] env: node: No such file or directory - oco hook unset
- all works fine
Relevant log output
2024-10-16 10:26:16.610 [info] > git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file - [18ms]
2024-10-16 10:26:16.610 [info] env: node: No such file or directory
2024-10-16 10:26:16.622 [info] > git config --get-all user.name [11ms]
2024-10-16 10:26:16.634 [info] > git config --get-all user.email [12ms]
2024-10-16 10:26:16.647 [info] > git config --get commit.template [12ms]
2024-10-16 10:26:16.647 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/main refs/remotes/main [11ms]
2024-10-16 10:26:16.662 [info] > git status -z -uall [14ms]
2024-10-16 10:26:16.676 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/main refs/remotes/main [13ms]
2024-10-16 10:26:16.688 [info] > git config --local branch.main.vscode-merge-base [11ms]
2024-10-16 10:26:16.700 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/origin/main refs/remotes/origin/main [11ms]
2024-10-16 10:26:17.729 [info] > git config --get commit.template [14ms]
2024-10-16 10:26:17.729 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/main refs/remotes/main [13ms]
2024-10-16 10:26:17.748 [info] > git status -z -uall [18ms]
2024-10-16 10:26:17.764 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/main refs/remotes/main [15ms]
2024-10-16 10:26:17.777 [info] > git config --local branch.main.vscode-merge-base [12ms]
2024-10-16 10:26:17.790 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/origin/main refs/remotes/origin/main [12ms]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with oco hook set, then commit through VS Code integrated source control and compare the result with oco hook unset. Investigate the hook entry point and the reported env: node: No such file or directory failure. Done means VS Code commits work while the oco hook remains enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript, node.js, vscode
- Domain
- developer-experience, devtools, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100