World domination feels imminent.
Hub Git Wrapper
11–20 of 23 posts
Re: Hub Git Wrapper
#12Earlier quoted context omitted.
hub works just fine to create a PR, some lack of RTFM is at play.
So, I never trust users to give me advice on features to add. But I always believe them when they say something is difficult or confusing. Research should not be required to make a good CLI do what you want, provided you understand what you want.
Re: Hub Git Wrapper
#13> hub is best aliased as git, so you can type `$ git ` in the shell and get all the usual hub features. World domination feels imminent.
Re: Hub Git Wrapper
#14Re: Hub Git Wrapper
#15> hub is best aliased as git, so you can type `$ git ` in the shell and get all the usual hub features. World domination feels imminent.
Re: Hub Git Wrapper
#16I once tried to PR from hub. It sent the PR from my branch on my fork to master on my fork. Obviously I wished to PR against the original thing I forked from. I just stick to the web interface now.
Re: Hub Git Wrapper
#17Edit: And per some concerns elsewhere in the comments, there's also a --dryrun parameter to ensure that it's going to do what you want it to do. ;)
Re: Hub Git Wrapper
#18Re: Hub Git Wrapper
#19> hub is best aliased as git, so you can type `$ git ` in the shell and get all the usual hub features. World domination feels imminent.
Re: Hub Git Wrapper
#20The release notes for version 2.2.0 mention their [cucumber specs](https://github.com/github/hub/tree/master/features), which look like a good example of using BDD in a full project.
And then I wandered off and got distracted by a UTF-8 problem in the Hebrew localization of Test::BDD::Cucumber.