Contributing or forking w/o being menaced by deployment failure emails

Right now, @dherbst and @chriscardillo have both forked and opened PRs to this repo. A challenge there is that the github deploy action will run and fail. The failure makes sense, but it's annoying to get emails every time it does.

It seems two use-cases we want to meet are:

* If I'm a **contributor to the CfP pipeline**, I want to open PRs without being spammed by gh actions
* If I'm **forking it as a template**, then I'm okay with meaningful notifications

@dherbst resolved by only running action when on this exact repo (https://github.com/CodeForPhilly/cfp-data-pipeline/pull/34). This works well for the first case, but @themightychris pointed out it causes issues for people using this repo as a template. Since we're still fleshing things out, and probably shouldn't be forked as a template yet, it seems okay to leave as is.

Opening this issue so we can explore how to also hit the forking use-case (I agree failures are useful here).