Received an email today from git about one of my repo. I just push to that repo from the editor.
You will need to change to authenticate with a personal access token instead of your password, but apart from that nothing should change I think.
2 Likes
What this means is that instead of using your GitHub password you use a one time randomly generated “app password” to login with with whatever you use to upload to git. The nice thing about this is it’s forced to be more random, and you can more easily revoke and regenerate app specific passwords. I’d guess when you generate app passwords you can specify which repos it has access to too / what features it is allowed to interact with.
1 Like
Yup, all sorted now, thanks everyone.
1 Like
Hi guys,
Decided against creating a separate question as what I’m asking is probably related to this anyway.
I use a private self-hosted git service where some of my Defold libraries are stored, and my CI pipeline uses Bob to build the game. My libraries are fetched from git via authenticated HTTP calls (typical https://login:token@git.service.yadayada stuff), and Bob has been working like a charm up until I updated it recently - I jumped from 1.2.172 to 1.2.177, and the authentication calls end up as Connection refused by the server at https://...
curl requests to these URLs work just fine - I remember there was an issue like that with Bob maybe a year ago, and I didn’t get to write a bug report because it got fixed fairly quickly, so I used Defold Editor’s builder meanwhile.
Now it seems like the way Defold Editor builds stuff is the same as Bob’s, so I can’t build the game with these custom dependencies at all, even from the Editor. What’s funnier, Fetch Libraries still works well and I can keep developing 
I believe it’s related to how Bob processes authenticated links, and as GitHub uses the same way of token-based HTTP auth, it’ll probably won’t work for GH private repos either.
@britzl, am I on the right track here?
I believe you’ve come across a problem we recently solved here:
The fix will be part of the 1.2.178 release (we release the beta today). You can try the alpha here to confirm that this solves your problem as well: http://d.defold.com/alpha/
2 Likes
Thank you, indeed it is the same issue! ETag explains why I couldn’t find it in GH issues (:
Made a mental note to test alpha builds for cases like this one in future.
2 Likes