Pair a dedicated CI sender key
Create a separate connection with npx -y notibuddy@^0.4.0 pair --to ci --label "GitHub Actions" and verify with doctor --to ci so you can audit or revoke CI independently in Connect.
GitHub Actions & CI/CD · Encrypted CLI
Drop a single NotiBuddy CLI step into GitHub Actions to send encrypted release approvals and build alerts directly to your iPhone—no Slack bots or third-party accounts.
Recommended · 30 seconds
Your AI coding agent will read /github-actions.md, walk you through pairing a dedicated CI key, and add a fail-closed deploy gate to your workflow.
Add NotiBuddy deploy approvals to this repo’s GitHub Actions workflow using https://notibuddy.app/github-actions.md (notibuddy@^0.4.0). Walk me through pairing a dedicated CI sender key in my own Terminal, tell me what GitHub Secret to save, and wire a fail-closed `nb gate` approval step. Your agent will read the full step-by-step runbook at notibuddy.app/github-actions.md (plain Markdown, English).
Pair a dedicated CI sender once locally, store its destination JSON in a protected GitHub Environment secret (NOTIBUDDY_CI_DESTINATION), then add this fail-closed Face ID gate:
- name: Set up Node.js
uses: actions/setup-node@v4
with:
node-version: '20'
- name: Request Face ID deploy approval
shell: bash
timeout-minutes: 15
env:
NOTIBUDDY_DEST_JSON: ${{ secrets.NOTIBUDDY_CI_DESTINATION }}
APPROVE_OPTION: Approve
DECLINE_OPTION: Reject
TIMEOUT_SECONDS: '600'
REF_NAME: ${{ github.ref_name }}
COMMIT_SHA: ${{ github.sha }}
REPO_NAME: ${{ github.repository }}
ACTOR: ${{ github.actor }}
RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
run: |
set -euo pipefail
if [ -z "$NOTIBUDDY_DEST_JSON" ]; then
echo "::error::Missing NOTIBUDDY_CI_DESTINATION secret."
exit 1
fi
umask 077
export NOTIBUDDY_HOME="${RUNNER_TEMP:-/tmp}/notibuddy-$$"
NB_PREFIX="${RUNNER_TEMP:-/tmp}/notibuddy-cli-$$"
trap 'rm -rf "$NOTIBUDDY_HOME" "$NB_PREFIX"' EXIT
mkdir -p "$NOTIBUDDY_HOME/destinations" "$NB_PREFIX"
printf '%s' "$NOTIBUDDY_DEST_JSON" > "$NOTIBUDDY_HOME/destinations/ci.json"
npm --prefix "$NB_PREFIX" install --no-save --silent notibuddy@^0.4.0 >/dev/null
"$NB_PREFIX/node_modules/.bin/nb" gate "Deploy ${REF_NAME}?" \
--to ci \
--sender "GitHub Actions" \
--message "${REPO_NAME} · ${COMMIT_SHA:0:7} by ${ACTOR} · ${RUN_URL}" \
--approve "${APPROVE_OPTION}" \
--reject "${DECLINE_OPTION}" \
--requires-auth \
--timeout "${TIMEOUT_SECONDS}" Use nb notify without --options to fire an instant encrypted notification when a workflow fails or finishes deploying:
- name: Notify iPhone on workflow failure
if: failure()
shell: bash
env:
NOTIBUDDY_DEST_JSON: ${{ secrets.NOTIBUDDY_CI_DESTINATION }}
REF_NAME: ${{ github.ref_name }}
REPO_NAME: ${{ github.repository }}
RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
run: |
set -euo pipefail
umask 077
export NOTIBUDDY_HOME="${RUNNER_TEMP:-/tmp}/notibuddy-$$"
NB_PREFIX="${RUNNER_TEMP:-/tmp}/notibuddy-cli-$$"
trap 'rm -rf "$NOTIBUDDY_HOME" "$NB_PREFIX"' EXIT
mkdir -p "$NOTIBUDDY_HOME/destinations" "$NB_PREFIX"
printf '%s' "$NOTIBUDDY_DEST_JSON" > "$NOTIBUDDY_HOME/destinations/ci.json"
npm --prefix "$NB_PREFIX" install --no-save --silent notibuddy@^0.4.0 >/dev/null
"$NB_PREFIX/node_modules/.bin/nb" notify "CI failed on ${REF_NAME}" \
--to ci \
--sender "GitHub Actions" \
--message "${REPO_NAME} · ${RUN_URL}" Create a separate connection with npx -y notibuddy@^0.4.0 pair --to ci --label "GitHub Actions" and verify with doctor --to ci so you can audit or revoke CI independently in Connect.
Save the full contents of ~/.notibuddy/destinations/ci.json as NOTIBUDDY_CI_DESTINATION inside a branch-protected GitHub Environment. You may remove the local file afterward—just do not disconnect it on your iPhone.
nb gate handles multi-window polling on one signed request ID up to --timeout and exits 0 only on a verified Face ID approval (2 on reject or missing auth, 3 on expiry, 1 on operational error).
Use nb notify --screen (or nb gate --requires-auth) to show canary KPIs, pre-flight checklists, and commit metadata on iPhone before promoting to production.
Send plan summaries or schema diffs to your pocket before terraform apply or database migrations execute.
Omit --options to fire a one-way encrypted push whenever a long release pipeline succeeds or fails.
Pair one iPhone with multiple local agents, editors, CI runners, and shell scripts—each with its own revocable sender key.