But there's an immediately obvious bug, the middle pane keeps resizing to become wider every time you switch between repos.
Also, one large repo I had simply shows 0 commits. It worked just fine before. And another even larger repo works fine.
231–240 of 248 posts
But there's an immediately obvious bug, the middle pane keeps resizing to become wider every time you switch between repos.
Also, one large repo I had simply shows 0 commits. It worked just fine before. And another even larger repo works fine.
Earlier quoted context omitted.
It's rather embarrassing that github would consider it too difficult or too troublesome to release Linux builds. Very insulting towards a huge chunk of its user base. Regarding GUI, how do you initiate a pull request on the command line?
I'm sure most hardcore Linux users would consider using a GUI to use git would be embarrassing / insulting TBF. I mean git add, git commit, and git push/pull is 95% of what you'd do with git and it's not rocket science.
Earlier quoted context omitted.
"Embarrassing"? "Insulting"? Aren't you taking this a little too personally? I mean, it's a software release for christs sake.
It demonstrates a lack of concern/acknowledgement of the diversity of its user base. Especially if they are going to be promoting this on the front page of their website and in my dashboard upon login, which presents me with the broadcast: "GitHub Desktop is now available The new GitHub Desktop is now available" And then I click on it to install it, I feel marginalized and hence a little insulted, when discovering I…
Its a shame that a Linux version is not included. A significant volume of developers work on Linux. If doing a multi platform application, why exclude it?
As strange as it sounds the lack of a decent git GUI is one of the reasons I don't feel comfortable using Linux as my main development environment (not the only reason of course). It's a big pitty neither Github nor Atlassian (the big "git" players, in my mind) seem inclined to release a GUI client for Linux.
Earlier quoted context omitted.
I think it's a myth that Linux users aren't interested in GUI tools. According to stack overflow statistics, Ubuntu is the most popular Linux based OS amongst developers, which is an OS that is much more GUI based than say Arch linux. According to the same stats, Linux and OS X usage is statistically tied at ~21%. If you take into account the fact that only about 2% of computer users run Linux at all it's pretty clea…
I don't think it's a myth, but it definitely is self-fulfilling (since it puts off users who would otherwise use Linux, but don't because they don't want to exclusively use the CLI) Personally I use a mac nowadays but still use and prefer the command line for this kind of thing. I tried using Github for Mac but quickly gave up the first time I had to do something vaguely complicated. I guess I'm still a linux person…
Its a shame that a Linux version is not included. A significant volume of developers work on Linux. If doing a multi platform application, why exclude it?
Having used a multiple of desktop systems since the mid-80's, and lots of their main IDE systems, I could never grasp this attitude. And yes, I do my way around Emacs and Elisp (but it comes from MIT Lisp culture).
Earlier quoted context omitted.
I don't think non-cocoa or non-WPF necessarily means worse quality, you just have to do a bit more custom work. Take Slack (using the Electron framework), or Telegram's Qt client. Having said that, Qt Quick Controls could definitely be improved by having better default desktop QML UI widgets.
I use Slack on a daily basis and I can't say I'm happy with it being an Electron app. For what it does it's very resource intensive and the way it disregards a lot of its host OS conventions isn't cool. If I wanted a web app I'd open another browser tab; there's no need for a goofy wrapper with half-hearted OS integration.
I'm on OSX and Linux, most of my team are on Linux, I'm not sure they would have taken the trouble to release a Linux version without Electron.
Earlier quoted context omitted.
I think it's a myth that Linux users aren't interested in GUI tools. According to stack overflow statistics, Ubuntu is the most popular Linux based OS amongst developers, which is an OS that is much more GUI based than say Arch linux. According to the same stats, Linux and OS X usage is statistically tied at ~21%. If you take into account the fact that only about 2% of computer users run Linux at all it's pretty clea…
Let me preface this by saying that I am a full-time Linux user and have been for several years. I run Debian on my laptop and Arch Linux on my home machine. Both use i3 (no DE), and I do all my work at the command line or in applications that I launch from the command line[0]. I love the Linux terminal. I don't even own a non-Linux machine, not counting the various OS X devices I've used at work when one is required.…
Would it not have been better if GitHub Desktop was a seperate application that gets permissions (for example via OAuth 2.0) as an application in the "Authorized applications" section of the GitHub profile?
Or am I missing something here?
Earlier quoted context omitted.
Some features I use: Cherry-picking commits across branches. Merging branches. Rebases for forward-porting your work onto a new upstream. Bisects for determining which commit introduced a bug. Push/pull for sharing. Format-patch for sending patches around. Submodules.
Two of these I haven't done: Cherry-picking (well I did once, it went so wrong I had to reset the repository), and Bisects. That sounds very useful.