R Gibim Drowze

GitHub GraphQL API v4 Examples

Here are two queries that look up information about a pull request via GitHub's GraphQL API v4. The first looks up a pull request by number, the second looks up a pull request by ref (i.e. commit hash, branch name, tag name).

Why tho

While it is trivial to use the RESTful v3 API to look up a pull request by number, the GraphQL API is the only way to do the same thing for an arbitrary reference in a single HTTP request.

These took a bit of trial and error in the GitHub's GraphQL Explorer and various support threads to get right, so I'm putting them up here for posterity.

Updating expired GPG keys and their backup 🔑🔐💻

I use a GPG key to sign my git commits.

An error like this one might be a sign of an expired GPG key.

error: gpg failed to sign the data fatal: failed to write commit object

Getting the Gist of GitHub Actions

Tutorial and tips for GitHub Actions workflows

Install and Create Emulators using AVDMANAGER and SDKMANAGER

TL;DR

For an emulator that mimics a Pixel 5 Device with Google APIs and ARM architecture (for an M1/M2 Macbook):

List All System Images Available for Download: sdkmanager --list | grep system-images
Download Image: sdkmanager --install "system-images;android-30;google_atd;arm64-v8a"

Project Ideas

Ok. I'm going to list off some ideas for projects. You will have to determine if any particular idea is good enough to include in a portfolio. These aren't creative ideas. They likely already exist. Some are way too advanced while others are simplistic.

I will recommend to post any project you make to github and make a github project page for it. Explain in as much detail as possible how you made it, how it can be improved etc. Document it.

If you pick an advanced idea, setup a development roadmap and follow it. This will show some project management skills.

Another piece of advice for those who are design challenged. Use different front end frameworks and use different themes for those frameworks to provide appealing designs without looking like yet another bootstrap site.

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages

	==Phrack Inc.==

	Volume 0x0f, Issue 0x45, Phile #0x0c of 0x10

	\|=-----------------------------------------------------------------------=\|
	\|=--------------=[ Attacking Ruby on Rails Applications ]=---------------=\|
	\|=-----------------------------------------------------------------------=\|
	\|=---------------------=[ joernchen of Phenoelit ]=----------------------=\|
	\|=---------------------=[ [email protected] ]=----------------------=\|
	\|=-----------------------------------------------------------------------=\|

	require "bundler/inline"

	gemfile do
	gem "rspec"
	end

	require "rspec/autorun"

	RSpec.describe "inline Bundler and autorun RSpec" do
	it "is convenient for self-contained examples & bug repros" do

	==Phrack Inc.==

	Volume 0x0f, Issue 0x45, Phile #0x0c of 0x10

	\|=-----------------------------------------------------------------------=\|
	\|=--------------=[ Attacking Ruby on Rails Applications ]=---------------=\|
	\|=-----------------------------------------------------------------------=\|
	\|=---------------------=[ joernchen of Phenoelit ]=----------------------=\|
	\|=---------------------=[ [email protected] ]=----------------------=\|
	\|=-----------------------------------------------------------------------=\|