A command-line tool that makes git easier to use with GitHub.

I have this in my .zshrc

eval "$(hub alias -s)"

• hub is installed via homebrew
• zsh completion is installed to /usr/local/share/zsh/site-functions

the hub commands like pull-request, browse etc doesn't get completed

Ideas @mislav ?

I can't open a pull request with hub. This is what I do:

$ git checkout -b new_branch
( some changes here)
$ git commit -m "Test commit"
$ git push origin new_branch
$ hub pull-request

And this is what I get from the last command:

(username and password lines)
Error creating pull request: Unprocessable Entity (HTTP 422)
field 'head_sha' is missing
field 'base_sha' is missing
base No commits between user:master and user:new_branch

It says "We don't support that file type. Try again with a PNG, GIF, JPG, DOCX, PPTX, XLSX, TXT, PDF, or ZIP." when i'm trying to upload a .ZIP file. I even tried changing the .zip to .ZIP in my file.

$ hub pull_request -i 836 github.com username: myusername github.com password for myusername (never stored): Error creating pull request: Not Found (HTTP 404) Are you sure that github.com/myorg/myrepo exists?

This repo exists and all other commands work except pull-request. Only for this command hub asks me for username/password

I am constantly hitting a HTTP 401 when trying to use

hub create

on my newly created project. Isn't the create action meant to auto create the project on github?

Steps: ~: mkdir -p helloworld
~: cd helloworld helloworld: echo 'trying out hub gem' > README helloworld: hub init -g Initialized empty Git repository in /Users/berinle/helloworld/.git/ helloworld(master) ✗: hub add . helloworld(master) ✗: hub commit -m "first commit" [master (root-commit) b770670] first commit 1 files changed, 1 insertions(+), 0 deletions(-) create mode 100644 README helloworld(master): hub create error creating repository: Unauthorized (HTTP 401) helloworld(master):

Please advice

What better time to request a feature in hub than moments after a feature is released in the GitHub UI! 😁 I love not having to go to the UI for common tasks, and I can see this new feature being included in my workflow for discussing a PR prior to wanting to merge it.

Reference: https://github.blog/2019-02-14-introducing-draft-pull-requests/

A cursory look at the API docs doesn't seem to have this available yet (I do see a "locked" flag), so this issue may hang out for a while.

I don't want to have a .config/hub file lying around on remote systems where I use hub. I'd prefer to communicate my password through the environment (since I can use ssh SendEnv, etc).

I've tried using GITHUB_USER and GITHUB_PASSWORD with a token generated from https://github.com/settings/applications, but when I try to send a pull request I get "404 not found". It works if I send a pull request by entering my credentials and using .config/hub. Any ideas?

I have hub installed, but when I run git push from a repository, I get this (and I'm pretty sure it's 2FA):

jkeiser@Ettores-MBP ~/s/chef-provisioning-aws> set -x GIT_TRACE 1
jkeiser@Ettores-MBP ~/s/chef-provisioning-aws> git push
Username for 'https://github.com': jkeiser
Password for 'https://[email protected]':
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/chef/chef-provisioning-aws.git/'

I am entering the correct password (I know this because if I curl --user jkeiser https://api.github.com/orgs and enter the same password, I get back this:

{
  "message": "Must specify two-factor authentication OTP code.",
  "documentation_url": "https://developer.github.com/v3/auth#working-with-two-factor-authentication"
}

I'd like for it to work. I'd LOVE for it to work by fixing git credential, because I'm using that from a Ruby library, but that's not this bug :)

Background

Initially this was just a small hack in my local hub repo. After having used it without any issues almost every day for the past two years, I thought I would open this PR for discussion to see if others are also interested.

Personally, I find it super convenient not having to open a browser/website to merge a PR (which I usually create from command line as well using hub pull-request).

Details

The GitHub API has offered a "merge" functionality for a long time:

PUT /repos/:owner/:repo/pulls/:pull_number/merge

See https://developer.github.com/v3/pulls/#merge-a-pull-request-merge-button

So far, this was not supported by hub.

I added a new hub pr merge <PR-NUMBER> command that takes the PR number and merges the PR (if the user has write access to the repo).

Note: This is the first PUT route - I had to add a PutJSON function to github/http.go.

Examples

$ hub pr list
      #1  Create README.md

# (Success case - PR 1 is merged, no output, exit code `0`)
$ hub pr merge 1

# (Error case, for example user has no write access)
$ hub pr merge 1
Error merging pull request: Not Found (HTTP 404)
Not Found

I also slightly updated the hub pr documentation to better reflect what it can do now.

$ hub
...
These GitHub commands are provided by hub:

...
   pr             Manage GitHub Pull Requests
...

$ hub merge
Usage: hub pr list [-s <STATE>] [-h <HEAD>] [-b <BASE>] [-o <SORT_KEY> [-^]] [-f <FORMAT>] [-L <LIMIT>]
       hub pr checkout <PR-NUMBER> [<BRANCH>]
       hub pr show [-uc] [-h <HEAD>]
       hub pr show [-uc] <PR-NUMBER>
       hub pr merge <PR-NUMBER>

Future ideas

Some ideas for the future (either as part of this PR or a follow up PR):

• Improve error messages
• Support different merge methods
• Before the merge, see if all checks are configured and have passed - if not, abort merge
• Allow "force" merging (if checks have not passed, see previous point)
• Allow customizing the merge commit message
• Add an option to automatically delete the PR head branch after successful merge

On GitHub Enterprise (GHE) v2.7.x, when I make a Pull Request (PR) with a single commit on a feature branch that is signed with a verified GPG signature, and eventually merge this in via the click action on the button labelled Confirm squash and merge, the commit is no longer signed with a verified GPG signature. So my question is, could GPG signed verified commit(s) status(es) from feature branches please be persisted into the branch it is merging into in the PR squash and merge process? Or even when using the Rebase and merge option? At least especially if there is only one new commit, which is GPG signed from a feature branch.

@mlang raised a good point at the end of his blog post about not being able to delete a fork.

What are your thoughts about this command delete? I see it useful in cases where I make a quick pull-request and then don't want to clutter my repos so I want to delete it right away. We could replicate the web interface by asking the user to type the name of the repo to confirm deletion. (We can also go a step further and only delete the repository if it's a fork?)

Hi! @matiaspedelhez

Microsoft Flight Simulator (XboxGames) Msfs_mouse_yoke-0.3c Wow! PERFECT. Microsoft Flight Simulator (Steam) Msfs_mouse_yoke-0.3c FAIL.

1. I uninstalled Microsoft Flight Simulator on XboxGames.
2. I installed Microsoft Flight Simulator on Steam.
3. Cmd opens msfs_mouse_yoke-0.3c and closes after 1

20221224T0415114592.log

I'm running hub release create inside GitHub Actions + Ubuntu 20.04 + Alpine 3.17. This error constantly breaks my Actions, this happens almost every time (but not always). The error is very cryptic. Is file size of the assets a problem? The largest of my assets is ~50Mb.

    runs-on: ubuntu-20.04
    container: alpine:3.17
    steps:
      - name: Install Prerequisites
        run:  apk add --update --no-cache libnsl libnsl-dev build-base coreutils cmake git xz wget perl gperf p7zip python3 strace && ln -sf python3 /usr/bin/python

      - name: Install Hub
        run:  apk add --no-cache -X http://dl-cdn.alpinelinux.org/alpine/edge/testing hub

Attaching 17 assets...
The release was created, but attaching 15 assets failed. You can retry with:
hub release edit build_757f82[13](https://github.com/busytex/busytex/actions/runs/3740840368/jobs/6349685778#step:10:14)e3624672ff516e9b3d8d5a6ae16400b3 -m '' -a build/native/busytex -a build/native/busytex.tar -a build/native/texlive/libs/freetype2/ft-build/apinames -a build/native/texlive/libs/icu/icu-build/bin/icupkg -a build/native/texlive/libs/icu/icu-build/bin/pkgdata -a build/native/texlive/texk/web2c/ctangle -a build/native/texlive/texk/web2c/otangle -a build/native/texlive/texk/web2c/tangle -a build/native/texlive/texk/web2c/tangleboot -a build/native/texlive/texk/web2c/ctangleboot -a build/native/texlive/texk/web2c/tie -a build/native/texlive/texk/web2c/web2c/fixwrites -a build/native/texlive/texk/web2c/web2c/makecpool -a build/native/texlive/texk/web2c/web2c/splitup -a build/native/texlive/texk/web2c/web2c/web2c

Error uploading release asset: Post https://uploads.github.com/repos/busytex/busytex/releases/86651807/assets?name=busytex: write tcp 172.18.0.2:47490->[14](https://github.com/busytex/busytex/actions/runs/3740840368/jobs/6349685778#step:10:15)0.82.114.14:443: write: connection reset by peer
Error: Process completed with exit code 1.

This will use dependabot to check any github action which this project uses for updates on a monthly basis in order to keep it up-to-date.

https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot

Command attempted: hub ci-status and hub ci-status --verbose

What happened: I have a repo with ~50 checks for CI. When a few of those checks fails, hub ci-status can incorrectly report success, and hub ci-status --verbose does not list all checks.

The number of results indicate that only the first page in GitHub's API pagination is handled.

More info: hub version 2.14.2

Command attempted:

I tried these commands to get the output of "hub sync": tmp="$(hub sync)" hub sync | read tmp read tmp < <(hub sync)

What happened:

echo "$tmp" always returns nothing

More info:

Did I miss anything?