setup-github

GitHub App Setup

Guide the human through creating and configuring a GitHub App for their wolt. Step by step, one at a time.

This skill is idempotent — safe to run again. If things are already configured, validate and skip.

Step 0: Check existing config

Check if GitHub App credentials are already configured:

grep -c "GITHUB_APP_ID" "$WOLTSPACE_WOLT_DIR/.env" 2>/dev/null && echo "found" || echo "not found"

If already configured: Validate the credentials work:

gh-app-token >/dev/null 2>&1 && echo "✓ GitHub App auth working" || echo "✗ Auth failed"

If working, tell the human and stop. If auth fails, continue to help fix it.

Step 1: Create a GitHub App

Tell the human:

Go to https://github.com/settings/apps/new and fill in:

• App name: anything unique (e.g. woltspace-yourusername)
• Homepage URL: https://github.com/jerpint/woltspace (or your fork)
• Webhook: uncheck "Active" — we don't need webhooks
• Permissions → Repository:
  • Issues: Read & write
  • Pull requests: Read & write
  • Contents: Read & write (for pushing branches)
• Click Create GitHub App

If the app is for contributing to woltspace, it goes on their own fork of jerpint/woltspace (Step 4), and the human opens PRs from the fork. Only a lodge the maintainer invites has its app installed on jerpint/woltspace itself. See "Contributing from a lodge" in the repo's CONTRIBUTING.md.

Wait for confirmation before continuing.

Step 2: Generate a private key

Tell the human:

On your new App's settings page, scroll down to Private keys and click Generate a private key.

A .pem file will download. Open it in a text editor and copy the full contents (including the BEGIN/END lines).

Paste it here.

Once they paste it, format for .env — replace actual newlines with \n so it fits on one line:

# The key should look like: -----BEGIN RSA PRIVATE KEY-----\nMIIE...\n...\n-----END RSA PRIVATE KEY-----