🚀 Create GitHub App

Create a GitHub App for the Update Flake Inputs action. This app will have the necessary permissions to create branches, commits, and pull requests for updating your Nix flake inputs.

ℹī¸ What is this for?

The Update Flake Inputs GitHub Action needs a GitHub App token (instead of GITHUB_TOKEN) to trigger CI workflows on the created pull requests. This form helps you create that app with the correct permissions.

📋 Complete Setup Overview

This tool is Step 1 of a 3-step setup process:

  1. Step 1: Create GitHub App (this page) - Generate a GitHub App with correct permissions
  2. Step 2: Configure Secrets - Save APP_ID and APP_PRIVATE_KEY to your repository
  3. Step 3: Add Workflow - Create the GitHub Action workflow file that uses the app

After completing this form, follow the instructions shown below to complete steps 2 and 3.

📖 View complete setup instructions in README

💡 Pro Tip

Fill out the form and click "📋 Share Form" to get a URL you can share with others. The URL will contain all your form data so they can create their app with the same settings!

The repository where you'll use this action. This will help generate a unique app name.
Choose a unique name for your GitHub App (auto-generated from repository)
Brief description of what your app does
📋 Required Permissions
Contents Write
Pull requests Write
Metadata Read
These permissions are automatically configured and required for the Update Flake Inputs action to work properly.

📝 What Happens After You Click "Create GitHub App"

  1. GitHub will open in a new tab with the app creation form pre-filled
  2. Review and click "Create GitHub App" on that page
  3. Install the app to your repository (you'll see detailed links below after creation)
  4. Step 2: Configure Secrets - Copy the App ID and save it as APP_ID in your repository secrets
  5. Step 2 continued: Generate a private key and save it as APP_PRIVATE_KEY in your repository secrets
  6. Step 3: Add Workflow - Create a workflow file that uses actions/create-github-app-token@v1 with your secrets (see example below)