zeke

# print output in a manpage-style pager
git whatchanged --since="1 week ago" -p content/v3

# pipe it to stdout
git whatchanged --since="1 week ago" -p content/v3 | cat

# pipe to a file and open that file in an editor
# (vscode highlights diffs, atom does not without a plugin)
git whatchanged --since="1 week ago" -p content/v3 > diff.sh && $EDITOR diff.sh

petrsvihlik

// This script shows how to use M language (Power Query Formula Language) 
// to read data from GitHub API v4 using a POST request.
// This can come in handy when building PowerBI reports that utilize GraphQL endpoints for loading data.

let
    vUrl = "https://api.github.com/graphql",
    vHeaders =[
			#"Method"="POST",
			#"Content-Type"="application/json",
			#"Authorization"="Bearer <your_personal_token_here>"

primetheus

SVN on docker!

Quick notes on setting up a lightweight SVN server that is accessible via http (WebDav) and the svn custom protocol (svn://).

credits to : https://medium.com/@elle.florio/the-svn-dockerization-84032e11d88d

Pre-reqs

• Docker (see 'Install Docker for Mac')
• SVN (should be installed on your Mac by default)

markerikson

// The classic AJAX call - dispatch before the request, and after it comes back
function myThunkActionCreator(someValue) {
    return (dispatch, getState) => {
        dispatch({type : "REQUEST_STARTED"});
        
        myAjaxLib.post("/someEndpoint", {data : someValue})
            .then(
                response => dispatch({type : "REQUEST_SUCCEEDED", payload : response}),
                error => dispatch({type : "REQUEST_FAILED", error : error})
            );    

anythingcodes

Generate GitHub Enterprise Issue from Google Form submission

To generate a nicely-formatted GitHub issue (even for GitHub Enterprise accounts) from a Google Form submission, you can use Google's script editor along with a GitHub personal access token that connects to the API. This is particularly useful when you need to triage bugs or feature requests directly to developers, but those who are submitting issues do not have access to your GitHub Enterprise instance.

Once this is up and running, on the development end, you can do some cool things within the body of each issue, like automatically closing GitHub issues via your commit messages and CCing your dev group or individual team members for each issue.

Here's how to set it up.

Step 1: Create Your Form

• Go to Google Drive and create a form with fields
• Click the Responses tab

subfuzion

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

bmcbride

Wiring up a Google Form to GitHub is not that difficult with a little bit of Apps Script automation. All you need is a Google account, a GitHub account, and a web browser...

Set up your GitHub Personal Access Token

Personal access tokens provide an easy way to interact with the GitHub API without having to mess with OAuth. If you don't already have a personal access token with repo or public_repo access, visit your GitHub settings page and generate a new token.

Be sure to copy your token some place safe and keep it secure. Once generated, you will not be able to view or copy the token again.

Set up the Form & Spreadsheet

1. Create a Google Form.

barrysteyn

Migrating From SVN to Git

This gist details the following:

1. Converting a Subversion (SVN) repository into a Git repository
2. Purging the resultant Git repository of large files

Migrating from SVN to Git is roughly split into three steps:

1. Retrieve a list of SVN commit usernames