Interesting Links for 28-08-2019

[andrewducker]

Jeremy Corbyn and other opposition leaders agree plan to stop no-deal Brexit

(tags:labour libdem europe snp uk hope )

No, the Great Central Main Line is not an adequate alternative to HS2

(tags:trains uk )

This is currently my favourite Git UI

(tags:git ui )

Renaming the Campbell Award

(tags:scifi awards racism )

Fuck Manchester Pride

(tags:pride Manchester OhForFucksSake lgbt )

On the new Amazon "Lord of the Rings" TV show

(tags:TV lotr )

Government to ask Queen to suspend Parliament

(tags:uk government doom europe )

US border officials are increasingly denying entry to travelers over others' social media

(tags:socialmedia immigration usa )

What are children dying from and what can we do about it?

(tags:children death )

Prorogue: The government takes its shot (with a much weaker hand than they'd like)

(tags:uk government hope )

Comments

[momentsmusicaux]

Not massively impressed with gitfork yet.

On launch, I can't see what to do. I have to create a new window BEFORE I open a repo? That goes totally against common UI patterns.

It offers to rescan for repos but doesn't tell me WHERE it's going to do that. It should tell me, and offer to let me change that.

It also beachballed for ages to open my current project repo, which other git clients handle fine. It's still thinking about it after a few minutes.

And there's no kind of support ticket system, no github repo, ironically.

Best thing I have found for visualising branches is GitUp, but I don't use it for commits (I can't remember why, there must have been a reason).

[channelpenguin]

We use GitLab at work and I am happy with the Graph on there. But we don't have a massively complicated branching system, just feature branches, develop and master (only ever updated from develop).

[andrewducker]

I really appreciate being able to click on two commits and get a instant list of the diffs.

[channelpenguin]

True, that would be handy. I use the GitHistory plugin in VSCode for that sort of thing.

[andrewducker]

Yeah, two of my team mates use the Gitlens plugin in the same way.

[momentsmusicaux]

It doesn't take a complicated branch system to turn git history into spaghetti. If you have about half a dozen feature branches that branch off from dev at various points, and then are merged in successively (without rebasing), you get something that most git GUIs render like total crap.