Skip to content

Instantly share code, notes, and snippets.

@queue-tip
queue-tip / pipeline-comparison.sh
Created December 7, 2023 15:13
Bash script to run ruby script with 2 versions of ruby and compare their outputs for diffs
#!/bin/bash
RUBY2=2.6.10
RUBY3=3.2.2
EXECUTABLE=$(basename "$0")
function usage() {
echo "NAME
$EXECUTABLE - Compares ruby-based pipelines for submission to Buildkite
@queue-tip
queue-tip / GitHub-Forking.md
Created September 14, 2023 13:57 — forked from Chaser324/GitHub-Forking.md
GitHub Standard Fork & Pull Request Workflow

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

Keybase proof

I hereby claim:

  • I am queue-tip on github.
  • I am jmartinez (https://keybase.io/jmartinez) on keybase.
  • I have a public key whose fingerprint is DB9A AF82 DD0E D2F1 9968 07CB 15CF 03A6 F9A2 59C8

To claim this, I am signing this object: