@AngularBones Thanks for your concern ❤️ we're all doing well! Sorry for the wait, hope you'll enjoy the new version we shipped today!
PS. We have a beta channel if you miss the update notification. DS
@Stuartq@haacked@FransBouma@david_whitney@terrajobst There’s always a chance, reports like yours as well as reactions in the issue all weigh in when we decide what to prioritize. If you have a use case or insight you think we should have that’s not already documented in the issue we’d love to hear it in the issue or here!
@haacked@Stuartq@FransBouma@david_whitney@terrajobst Yeah sorry, GitHub Desktop doesn’t have a built-in way of opening an external diff/merge tool. I think this is the most relevant issue: https://t.co/pFXtj0TlVX
We just shipped a update to GitHub Desktop with a beta version of our brand new dark theme! If you're a fan of dark themes I'd love it if you could try it out and let us know if you find any rough edges https://t.co/cmcbW8VrR4
@shiftkey @paulcbetts @donokuda I know of no one better suited than @paulcbetts to contribute a fix to sass-loader that’ll fix the underlying cross-compile problem and will benefit a much larger audience than changing desktop over to less 😝
@nehayward Not at the moment, no. If this is something you’d be interested in contributing it’d be great if you could open an issue about it at https://t.co/4Q1Kh1Iupb and describe your use case
@rajula96reddy@GitHubDesktop@ubuntu Glad you like it! The app builds and runs on Ubuntu if you compile it yourself and there’s unofficial builds as well but we’re looking for help from the community to get it to a state where we could ship official builds. See https://t.co/n65ryFveQP
@shiftkey@slace Express train is 5 hours, flight is 1 hour. Train is usually less than half the price of flying and even less factoring in transit to/from the airports. The trains are nice, scenic and have bistros/wifi/power on board. Flying is a bit more reliable
@einonm The kernel already uses Co-Authored-By! See https://t.co/AhQwZk7roJ✓ the basis of this is not GitHub specific, it's an agreed-upon way of adding well-formatted information trailers to a commit message that came out of the Git project https://t.co/sh7qmo4Rgr
@magnetikonline@github I thought it felt weird to have them at the bottom too at first but that’s a presentation concern. Tools could present in other ways. It makes a lot of sense for the other suggested trailers tho like “Fixes: nnn”. Having an agreed upon format for those will make tools better
@magnetikonline@github I doubt there’d be any noticeable performance hit, author and committer are stored the exact same way only at the top of the commit object. Totes agree with the command line tho. Have a read through the git interpret-trailers docs. There’s already a lot of support for automation
@CoenJacobs Totally. It’s personal preference really, they weigh the same on GitHub. For me, if I just made some style tweaks I’d let them stay the author and just be the committer. But then I rarely rewrite commits so I’d just add another commit with my changes
@dinesharjani@romenrg@github It’s not GitHub-specific although the username autocompletion in Desktop obviously is. It’s an agreed upon trailer in the commit message. The Git project have used it for a while. See https://t.co/8AjCFQNb68
@magnetikonline@github It kind of is already. This is the approach that Git project contributors use. It adds an agreed-upon trailer to the commit message and there's tooling in Git already to parse it. I'm sure there'll be more support in the future though. See https://t.co/8AjCFQNb68
@tammofreese Sorry, I don't have a good estimate. Keep a good look out for the GitHub Enterprise changelogs though, shouldn't be that long! You can start using it in GitHub Desktop today and ask your admin to rebuild contributions for you when you upgrade Enterprise
@letientai299 You can build it from source and run it on Linux today but we're looking for help from the community to get it to a point where we could package it, see https://t.co/gsTUVaaLqu