Open a pull request from command line

Mon, 23 Oct 2023 11:27:01 +0300

When ready working on a feature branch in a project that uses GitHub, GitLab or anything else like them, one generally do git push -u origin and then goes to the web interface to open a pull request. Pretty much all of these platforms provide the URL to go in order to spare a few clicks. For instance:

❯ git push -u origin baba
Enumerating objects: 1, done.
Counting objects: 100% (1/1), done.
Writing objects: 100% (1/1), 181 bytes | 181.00 KiB/s, done.
Total 1 (delta 0), reused 0 (delta 0), pack-reused 0
remote:
remote: Create a pull request for 'baba' on GitHub by visiting:
remote:      https://github.com/user/project_name/pull/new/baba
remote:
To github.com:user/project_name.git
 * [new branch]      baba -> baba

A few years ago Rado Stankov wrote a great post about a few git aliases and scripts he uses to automate things: Git Tricks . I took literally all of the tricks he shows there in my dotfiles and strongly suggest for you to do the same.

One of tricks there is a git-pull-request scripts which allows automating that clicking on the provided link with a git pull-request command. Over time however, I’ve started using GitLab and this trick no longer works for that, as it assumes you’re pushing into a GitHub repository. So, I had to modify that script in order to be agnostic of the hosting you’re using and simply open whatever URL the upstream provdes on push (which to be fair, might be a bit risky, if you’re pushing to a shady git hosting, so use it with care):

#!/bin/sh
current_branch=$(git rev-parse --abbrev-ref HEAD)
git push -v --set-upstream origin "$current_branch" $2 2>&1 | while IFS= read -r line
do
	echo "$line"
	url=$(echo "$line" | grep "remote:" | grep -Eo '(http|https)://[^ ]+')
	if [ -n "$url" ]
	then
		xdg-open "$url" > /dev/null
	fi
done

Note that as a linux user, I’ve changed open to xdg-open. If you’re using macOS, might what to do s/xdg-open/open/ over this.

If this is saved in a file named git-pull-request with execute permissions (+x) at some of the directories listed in your $PATH, running git pull-request will push your current branch upstream and output exactly the same as above, but also open the provided link in your default web browser (presumably in a new tab).

git bisect

Mon, 01 Jan 0001 00:00:00 +0000

git bisect provides easy to use binary search approach in order to find a bad commit. This tip assumes you know how it works is in general, but always forget what the commands are precisely.

Prepare a single command that tries to reproduce the bug (e.g. script, test) off tree. Bisect is about to start jumping around, so it can’t be in the tree.
git bisect start: begin the bisect session.
git bisect bad: mark current HEAD as a bad commit (i.e. the bug is reproducible).
git bisect good : some known commit in the past, where the bug does not exist.
You get dropped at a given commit. Try the command/test/script from step 1 and:
- if the bug exists: git bisect bad
- if the bug does NOT exist: git bisect good
Repeat until the initial bad commit is found.
git bisect reset.

git bisect run

Steps 5 and 6 can be automated with git bisect run if you can provide a script that exits with status code 0 when the chosen revision is good and something between 1 and 127 (except for 125) when the revision is bad.

The script should obviously be out of tree and executed with:

git bisect run [ ...].

Git on Kiril Vladimirov

Open a pull request from command line

git bisect

git bisect run