Github is one of the most important tools in a developer’s arsenal. However, as easy as it is to pick up and learn, Github can actually be rather complex when working in large-scale deployments and the occasional bug and glitch isn’t anything surprising to come across.
In this article, we’re talking about the “error obtaining VCS status: Exit status 128” issue, its causes and what you can do to fix the problem.
What causes “Error obtaining VCS status: Exit status 128”?
The error is generally triggered when there’s an issue with the version control system (VCS) status. This can be caused by a number of factors:
- Internet connectivity issue
- The Git repository is owned by someone else or is unsafe
- Github servers are experiencing an outage
Also read: Intel wireless ac 9560 not working: Quick Fix
How to fix “Error obtaining VCS status: Exit status 128”?
Here are two fixes you can try out.
Disable VCS stamping
The first and easiest way to fix this problem is by simply disabling VCS stamping by using the following command during the build process.
Do keep in mind that this can cause issues later down the line, especially when it comes to Git as you won’t have the version control information embedded in the built binary files that can cause confusion later down the line.
Add a safe directory in Git
Alternatively, you can also mark a directory safe in Git using the following command.
git config --global --add safe.directory [your directory here]
Doing so will explicitly mark the directory as safe and Git won’t generate any VCS stamping warnings. Do keep in mind to only do this when you’re absolutely sure that the directory you’re pushing to is in fact, safe.
Also read: How to create a Git repository? How to connect it to GitHub?