no .git folder
See original GitHub issueminikube Make uses git log for getting the commit sha for minikube version,
git log doesn’t work in checkouted source code
when I run git log --pretty=oneline
I get this error:
Not a git repository (or any of the parent directories): .git
Issue Analytics
- State:
- Created 3 years ago
- Reactions:22
- Comments:24
Top Results From Across the Web
Where is my local repository? (no .git directory) - Stack Overflow
Go to explorer · Select Organise · Select Folder and Search Options · Select View tab · Check Show hidden files, folders and...
Read more >What is .git folder and why is it hidden? - Tutorialspoint
The .git folder contains all information that is necessary for the project and all information relating commits, remote repository address, ...
Read more >What is Dot Git Folder in Git and What happens if we delete ...
As you notice, .git is not present in the list. By this, we have deleted our .git folder and the entire work we...
Read more >How to Fix the “fatal: not a git repository” Error - ContainIQ
Make sure you correctly typed the name of the directory. · Check that you correctly created the repo. If the directory doesn't contain...
Read more >I lost my .git folder. I have a copy of the structure on my local ...
You can just git init in that directory and start a new repo but there is no way to get your old commits...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was using
self-hosted
runner. And it had no.git
folder showed me logs as below:This means, the repository got downloaded using the GitHub REST API, which meant to dowloaded differently.
So for debugging what’s going around, I tried on the
ubuntu-latest
instead ofself-hosted
and it showed me log something like this:After comparing those two logs: one is using Git version:
2.17.1
, and another one is using Git version:2.28.0
.Hence, after updating the Git version (>= 2.18) into latest one, the issue got resolved in my case.
Self hosted: upgrading git for debian-based distros:
Either run it before the
checkout
action, or, if the runner is a docker container, add as aRUN
command