Hi Yoel,
I can understand that you are having trouble while performing “Source Control” setup and interface. The erroneous setup has caused corruption of the repository.
Please know that the errors shown on the console does not pinpoint to an exact cause of the issue. However, there seems to be an error in the Git repository while attempting to commit the files. The following explanations might explain the issue and guide you through steps that you can follow to troubleshoot and resolve the problem:
- Corrupted repository: It's possible that the repository has become corrupted due to some unknown factors. In such cases, creating a new repository and recommitting your files may be the simplest solution.
- Google Drive synchronization: Storing your repository on Google Drive can sometimes cause synchronization issues, especially if multiple devices are accessing the repository simultaneously. Try temporarily disabling Google Drive synchronization for the repository and see if the issues persist.
- Git configuration: Double check your Git configuration to ensure that it is set up correctly. Verify that the remote repository URL is correct and that you have the necessary permissions to push to it.
- Git object integrity: The errors related to bad object pointers and invalid “reflog” entries suggest possible corruption in the Git objects. You can try running ‘git fsck –full’ with the ‘--lost-found’ option to attempt to recover any lost objects or repair the repository.
- Local repository cleanup: If the issues persist, you can try cleaning up your local repository by removing any unnecessary or corrupted files. Make sure to back up your repository before attempting any cleanup operations.
Kindly refer to the following Git User Manual, under the subsection “Recovering from repository corruption” which consists of snippets of code that will be helpful in recovering the repository:
Hope this helps.
