Skip to content

Instantly share code, notes, and snippets.

Avatar
🍕
saucin chief

Brian Douglas bdougie

🍕
saucin chief
View GitHub Profile
View github-actions-fetching-upstream.yml
name: Fetch Upstream
on: pull_request
jobs:
fetch-upstream:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@master
- name: fetch and push
View sign-off.yml
name: Sign off commits in UI
on:
pull_request:
paths:
- '*.md'
jobs:
sign-off-commit:
name: signing commit
View explanation.md
Explanation

Your account was auto added to the org by a few ways. Here is the explanation on how that happened.

The actions workflow, auto-approve.yml, is trigger on all pull requests. During this triggered worfklow 3 synchronous actions. They syncronous because of the steps flag in the YAML, which we will cover.

  1. hmarr/auto-approve-action@v2.0.0 - An action that approves PRs automatically
  2. bdougie/label-when-approved-action@master - An action the adds a specified label when approved (forked from puill-reminders/label-when-approved-action)
  3. bdougie/automerge-action@master - An action that merges pull requests with the "automerge" label. (forked from pascalgn/automerge-action)
@bdougie
bdougie / README.md
Last active Jan 10, 2019 — forked from DEGoodmanWilson/README.md
Giphy and GitHub
View README.md

Goals:

  1. Learn how to set up Probot to create a GitHub App boilerplate
  2. Learn what a GitHub Event is.
  3. Learn how to tell Probot to react to Events by calling external APIs

Let's begin with a warmup. Imagine that we want to greet new visitors to our open source project, by sending them a gif when they open a new issue.

Part 1: Hello World

Begin by making a sandbox repository, to keep everything nice and contained. https://github.com/new

View genesis_public_key
04b10296819c3ed4099f0e473c94223a08b6c55ad9697f2efc612a98a61feeb331a548213df9d9018b75c1e1b586074fc5f718c9404711f66a3cd249151320bfbe
View debug.rb
# the problem is return the wrong answer, set a breakpoint to find out what is wrong
def powersOfTwo(n)
newArr = []
(0..n).to_a.each_with_index do |x, i|
# set a print to see what s happening
newArr.push(2*i)
end
newArr
View meeting.md

The Main Content

This is where we carry out the plan from the first step. This can take a lot of different forms depending on where the student is and what they need.

The "Help, I'm Stuck!" Meeting

This is a common type of meeting when the student is stuck on something they’ve been working on and are trying to figure out how to get things working again. This is a great opportunity to pair program on debugging skills, walking through the problem solving steps together. Sometimes as a mentor you’ll know what the problem is right away, and sometimes you’ll be just as stumped as the student, but either way walking through a debugging process is very helpful. The process might look like this:

  1. Have them describe their understanding of the problem and what they’ve tried so far to resolve it.
  2. Confirm the problem together and have them walk through recreating it slowly to confirm that what they think is the problem is actually the problem (it often isn’t).