https://www.sourcetreeapp.com/
If GitHub had built Twitter:"Yeah bro all you have to do is open the CLI and type...
< rebase that mf >
bork
zomg n00b ur screwed
rebase that mf
submit pull request for tweet
ssh -T billy.anyteen@github.com
# Permission denied (publickey).
rebase that mf
pull tweet again
ssh: connect to host github.com port 22: No route to host
aargh
rebase that mf
error: The requested URL returned error: 401 while accessing
# https://github.com/user/repo.git/info/refs?service=git-receive-pack
# fatal: HTTP request failed
ssh -T git@github.com
# Hi username! You've successfully authenticated, but GitHub does not
# provide shell access.
If ButtPlug, I mean GitHub, seems like this to you: get SourceTree.
If using ButtPlug's idiotic attempts at building user interfaces make you wish you were doing something more fun, like cataloguing leech species of the Amazon by picking them off your genitals, get SourceTree.
If reading ButtPlug docs makes you want to kill kittens, tell them where they can stick their docs because you have SourceTree and will never need to read ButtPlug's docs again. :D
SourceTree: receiver of the Official Antechinus Seal of Approval. 8)
(srsly, GitHub becomes quite usable once you figure out how to totally avoid any of their docs and interfaces)
(get SourceTree)
(srsly)
Now that is some ROFL funny ! Picking leech species LOL .. I don't who comes up with this stuff but its gives me hope for mankind :D
So have you tried SourceTree? Cool that its from Atlassian, I use BitBucket for some stuff and in some ways its better than GitHub, but both use (or can) use Git as the source control. I just use tortoise git and have a flow that works for me these days, but I've been through a lot of pain with git and what commands to use.
Yeah I've tried it. Haven't done an awful lot with it yet, but I have a forked 2.1 repo on ButtPlug, and a synched-to-2.1 local repo on desktop now, and I can use all the basics easily and without swearing. That's a big advance over where things were before.
I'm even contemplating submitting pull requests. Don't faint now. :D
Here, to save you the trouble of logging in at SMF, some choice excerpts from my initial ranting. After downloading SourceTree and doing a bit of inspired ranting, the SMF crew told me the basics of using SourceTree just to shut me up. :D
It works too. SourceTree = No commandenlinen stuffz at allen (unless you actually want to).
Lol I have read it, when I saw "Haz shiny buttons?" I just started to laugh loud ;D
So after a lot of back and forth over at SMF, including well-meaning but woefully misguided souls attempting to get me to do things "the git way", I have now got it all sorted for sane people who just want to test a bit of code and get on with it.
Ok so all the average mug needs to know is:
1/ Sign up at ButtPlug (sad, but necessary).
2/ Fork a repo over to a new repo of your own.
3/ Do not, under any circumstances, download anything ButtPlug suggests that you download. If they built it, avoid it like the plague. If you fail to follow this step, you will regret it.
4/ Ignore any twat who has the temerity to suggest that you should waste your time looking at any web page than even mentions the CLI. You don't need it, and it will only screw you up.
5/ Get SourceTree. :D
6/ Ask Sourcetree to haul your repo down to desktop. It will do this if you push shiny buttons. SourceTree is nice. :)
6/ Do not make branches. Do not listen to anyone who says you should make branches because "it's a git thang", and refuse to look at any web page that has gruesomely-coloured pictures of supposedly cool branch diagrams that would make Salvador Dali reach for his opium.
7/ Copy files from the desktop repo over to your local host test site. This is why you don't want branches. New branches don't actually make any new files for you to copy to your test site. New branches only make new sorta virtual files that don't really exist. This means they are useless for what you want to do.
8/ Frig around with the files on your local test site until they only break browsers you don't care about (ie: everything except Gecko).
7/ Copy edited files back into desktop repo.
8/ Push changes to ButtPlug (stage chunks, commit, push).
Sorted. :P
It may not be l33t, but it works. 8)
Beats me why the gently caress they didn't just tell me this in the first place. Would have saved a lot of time.
You can do whatever you want, but this will screw your repo more than another any other thing you may do, but you like shiny buttons so go for them. ;)
And I'm not saying it because I read it on some web page, but simply because I didn't do it at the beginning and I screwed my repo several times.
9/ If repo goes personal floatation device up, make new repo. Making new repo is easy, and you will have backup files on your local test site.
Sounds like you have something that will work for you and maybe some others ... keep your opium close by though ;)
Oh hey, this is just my basic foot-in-the-door strategy for the average mug. I'm not suggesting it's the optimal way to go for experienced power users in control of complex projects. I also realise that if I keep using this stuff long enough I'll just naturally pick up more tricks along the way, which can then be incorporated as and when I think they're useful.
What I'm after at the moment is deliberately keeping the barrier to entry as low as possible. As an analogy, I didn't start theming by reading the entire PHP manual. I started by picking up what I needed to know at the time while I was trying to do something specific. This is a similar approach, so that all the time and energy that would normally be spent swearing at GitHub can be spent swearing at forum code. ;D
Yup I get that ... and its a good thing to find something that works for folks who just want to support a project, Git can be a block for some, Took me a long time to get something that worked for me, but I have a lot of branches to deal with.
Should you decided to swear at the Elk code, do so on the development branch, thats 1.1 code and is currently being thoroughly abused and is somewhat broken at this time as well O:-)
https://github.com/StealthWombat/How-to-fork-an-Elk
Its a bit broken right now due to the removal of bg bg2 divs everywhere, have not fully sorted the css / templates to account for that so some padding / margins / shadows / backgrounds are a bit off.
Hey if you want me to be evil, I have a nice list of about 40 or so issues I think should be fixed in 2.1 Beta. If I add them all to the issues list in 2.1 they'll have a list bigger than your 1.1 list. :D
Oh hang on, then they'd want me to fix them all. Hmmm. :P
LOL .. I wish all of the 1.1 issues were actually in the tracker, would make it seem like we are making better progress :P
We have soft goal to have a 1.1 beta in about a month, but we are still in the fun part of breaking stuff, so I don't think it will happen. Its a good goal though, will happen before the end of year, but till then its fun in the thunder dome.
Endish of the yearish sounds fine. Christmas is always a good time for presents. Throw a Santa in the linktree home for 1.1 beta. :D
Humm ... maybe this wombat santa :P
I guess I can see the target audience for this software, but to be honest, this seems hugely bloated and time-wasting. What is wrong with the standard Git CLI aside from being a small learning curve at first?
I guess the usual problem with CLI: it looks complex. ;)
I can't speak for everyone, but I think the solution to that is a tutorial, not a GUI.
You really don't get it, do you? There are already plenty of pages on the web documenting use of the CLI for GitHub. Making a few more isn't going to change anything. Some people just don't want to use CLI. Why do you think GUI's of any type were invented? Do you think we should all still be operating our PC's via DOS?
SourceTree may be "bloated" if your primary concern is getting the job done with the minimum of code. A lot of people don't care about this, and why should they? It works. It runs just fine. The code behind it isn't a problem. It does the job.
I don't find it timewasting at all. I find it fast and convenient to use. Given the popularity of SourceTree, it's obvious I'm not the only person who feels like this. If you prefer CLI, go ahead and use CLI. Nobody who prefers SourceTree is going to care what you use. Suit yourself.
GUIs were created for tasks where the required typed commands would be too much more effort than learning the layout of a GUI and which buttons perform the commands when clicked. For something as dead simple as Git, it's always faster and simpler to just type the commands out. I'm just saying that most people are going to find it much more beneficial to understand the Git CLI than having to install and then learn how the buttons translate to actions on a GUI.
Well I think you are making quite an assumption there. I don't need to know how the buttons translate to commands. I don't like typing commands. I prefer clicking buttons. I don't care how Git works as long as it works. How it works is not a topic that interests me. I can drive a car without doing a mechanic's apprenticeship for years. Some people just want to get to work and back.
But if you want to make tutorials, go ahead and make them. As I said, there are plenty around already. I can't see more of them making any difference, unless you think that all the previous ones were made by people who were too dumb to know what they were doing.
Edited my post to reflect my meaning. The buttons and commands both translate to actions. The commands are easier to understand than buttons on a GUI. As I said above though, I can't speak for everyone and it's subjective. But in my opinion, it's easier to understand the outcomes from typing the commands than pressing buttons. And as you said, it's already very well documented.
Commands are simple in that they "do what they say on the tin":
git branch
List, create or delete branches
git pull
Grab a remote
git push
Update a remote
git checkout
Checkout a branch
git commit
Commit changes
All these commands just do exactly as you type them. It's plain English, which I think is much easier than learning yet more software.
This is stated as fact rather than suggested as opinion. In that respect, it conflicts with your next sentence.
So you admit that commands may not be easier to understand than buttons? :D
The outcomes from pressing buttons are very easy to understand. You press a button. Something happens. You press it again, and the same thing happens again. It's really not terribly mysterious.
Don't get me wrong, I'm not saying you're incorrect. Not everyone is going to see it the same way. I'm just saying that for me, and I think for most, it's easier to tell the machine what to do in English than learn yet more software with more interfaces and buttons and symbols, etc.
Of course I admit that, why wouldn't I? Everyone's brain works in a different way. On a logical level though, commands make more sense.
And I found learning the software was a piece of cake, and much more pleasant than frigging around with the CLI. :)
I think it all depends on what you need to achieve with git. If you never intend to be more than a casual user the a simple GUI, with single install, that gets the job done is great. Perfect for those that want to supply a few lines of code here and there, every now and again. The entire concept of git has been a real roadblock for some.
Now if you are going to do more complex operations then at some point the CLI is going to be the only solution. But if you are not the repo owner and not worrying about merging in various feature branches or cherry picking fixes from some branch or the always joyful merge conflicts or whatever then the CLI is probably to much. And if you don't use it a lot, you will forget the commands or the parameters.
I was going to give this tool a look, but I'm so dreadfully worried that adding in yet another git tool will mess up my environment, which is such a mess anyway. I use a mixture of CLI (especially when I'm on *nix) or since git support is built in to my IDE, I use that quite often as well.
Okay, so you admit that I'm right. Everyone's brain works differently and some are going to find the command line much easier, especially with the sheer amount of documentation. This GUI does not objectively make anything easier, just a longer process.
Ok, so why do you think that making more tutorials is going to persuade people who have already seen a stack of tutorials, but prefer a GUI? Surely you are aware that its reliance on the CLI has always been one of the main things holding back wider acceptance of Linux as an everyday OS. Linux enthusiasts keep making the same argument you're making now. It doesn't work for a lot of people.
No. However I'm happy to admit that you're determined to be right. :D
Why would I make more tutorials when there is already a heap out there?
Likewise it would appear. You're not very good at seeing a middle-ground, are you?
Dunno, but earlier on you were saying you thought a tutorial was the solution, rather than a GUI. Since there are heaps of tutorials already and they obviously aren't working. I thought you may have been intending to make another one. Motoko over at SMF had the idea that if
he made tutorials suddenly everything would be different.
I've already said that I'm perfectly happy for you or anyone else to use CLI if they prefer it.
No, they're aren't working for
you. Understand that other people find the command line easier to use. It's not difficult to realise different people have different perspectives. I'm not going to make yet another Git tutorial when there's plenty about that work perfectly fine for the majority of people. Even GitHub has some pretty slick tutorials on the Git CLI.
A GUI app may be great for you, but it's not the be-all and end-all solution for everyone. I'm trying to make the point that other people (and I'd argue the majority) are perfectly happy with the Git documentation out there and the written English of the CLI commands.
This doesn't mean I'm taking any value away from your GUI suggestion which will be perfectly valid for a subset of people.
Wasn't really looking for your permission, I was trying to help you understand why other people find the CLI easier, but I'll take what I can get. I don't know how this got blown into such a long conversation lol.
I was simply pointing out that I wasn't arguing against anyone using the CLI if they prefer the CLI. You seemed to think I wanted to ban the CLI or something.
I was trying to point out that different people will find different solutions easier. You seemed to think that I was saying the GUI was worse.
Ok, so we agree that anyone can use WTF they like.
:-[
Well then WTF are we arguing about? ;D
The internet is 99% embarrassing. You'll get used to it.
I honestly have no idea :D
I blame Wizard.
Dear diary,
This morning I had to update my local repo on desktop and my forked repo on ButtPlug. I had to do this because people at Elkarte are evil. They actually work on stuff and make changes, unlike the SMF repo which is static for yonks. :D
Updating my repos was really slow and painful. I made my first cup of coffee for the day, realising halfway through the process that no, I could not just pour the boiling water straight into my mug and get coffee. I had to pour it into the coffee plunger first, then into the mug.
Once the coffee-making process was sorted via Nature's pre-installed GUI, I then had to open SourceTree and fix the repos. This was a truly terrible experience. I already happened to have the Elk dev branch open from last time, so I was the forced to undergo the ordeal of clicking the button that said "Pull", then selecting the remote repo and branch I wanted to pull from. Then, as if this wasn't painful enough already, I had to click the "OK" button too. Why, oh why, did these evil bastards make things so difficult?
It got worse. I then had to watch a funny blue thingy go across the progress bar while I kicked back and sipped coffee. I'm thinking of complaining to the UNHRC about this. Seriously, I need some sympathy here.
And think there are about 120 bugs open targeted at 1.1 beta 1 that is meant to be released in about a month. xD
Yeah Spuds mentioned that was a "soft target". I'm thinking it's probably very squishy indeed. :D
LOL, you have my sympathy!
You have to love timezones ... 13hours ago I was sipping my morning coffee, now I'm enjoying my evening imbibe! Up next, I'm about to watch some silly screen blurt out a bunch of stuff while I sip it. Then again if you are hard core, I suppose timezones don't have anything to do with that :D
Shhh I have not convinced emanuele just yet, he may need some gentile caressing.
HA, I'm just warming up, now that 1.0.5 is out I can really run wild :P
Right now I am
so wishing I had listened to those people who told me to use the CLI.
Don't make the same mistake I did, kids, or you too may find yourself lying in the intensive care unit of a secure detox facility, constantly looking over your shoulder for cartel hitmen.
1 week down to 99!
Yeah, it's true I moved some to beta 2, but that's part of the game. :P
I appreciate your efforts to maintain the release dates and I understand it's not an easy task. Have some sleep and relax sometime ;)
Even if it will be released a few month later I will still use Elkarte :D
I'm working to increase that :P
That's ambiguous!! LOL
And another week later down to... 98. xD
Ok, this week has been quite. O:-)
Let's try with the next one, I'll have a different shift so I may be able to either sleep more or work more, we will see. ;D
I've fixed a few in the branch I have open, although I don't think many of those were reported. All things I found will playing with the httpreq class ... gets around 130 scruit issues as well. Unfortunately I'm nowhere near done :'(
For all git fans!
http://xkcd.com/1597/
:P
After trying to deal with that GitSh.. GitHub, I am all in for ANYTHING other than that.