Closed henesy closed 5 years ago
That definitely looks like a bug in dgit to me, I don't see anything wrong with that config file.
Want a tgz of the repository?
If it's easy to put somewhere. I spent a couple minutes trying to reproduce by deleting things from the .git directory after doing a clone but only managed to break things in different ways.
I couldn't say exactly what I did to produce this state, I apologize.
I'm pretty sure in the case of this repository it was made from git init
and I added the remote/origin later. I'm not sure what commands I ran at the time, but I probably went off dgit output.
There's no file ".git/refs/remotes/origin/master" in the tarball,so neither dgit nor git can push it. I think #253 should prevent it from happening in the future. To fix your local copy, you should be able to just copy .git/refs/heads/master
onto .git/refs/remotes/origin/master
Ahhhhhh that makes sense many thanks as always :)
I’ll test my repo soon
I can confirm my repo works with quick fix!
I didn't realize this was a thing, thank you :)
it was supposed to be created when you did the first git push (or when you do a git clone/fetch), but there was a bug with where dgit push
didn't create it since you created the repo with git init
That makes sense ya
I'm not sure if this is a real issue or not, but I had a repository somehow end up in a state where it could not find origin/master on git pull.
I can push just fine, and other repositories pull fine, but one I was working in now does not pull.
This might just be something dumb I did and don't remember.
Log: http://okturing.com/src/6786/body