Skip to main content

Create a New Installation

Create a new Spec-Up-T installation directly from your browser—no local setup required!

Running the "Create Spec-Up-T Project" Workflow

This guide explains how to use the "Create Spec-Up-T Project" workflow to generate a new Spec-Up-T project repository. Since this workflow requires write access, you’ll first fork the trustoverip/spec-up-t repository and run it from there—all via GitHub Actions in your browser!

Prerequisites

  • A GitHub account.
  • (Optional, but strongly recommended) A Personal Access Token (PAT) with repo and workflow scopes if you want the project pushed to your own repository. If you skip this, you’ll get a downloadable artifact instead.

Steps to Run the Workflow

  1. Fork the Repository:

    • Go to https://github.com/trustoverip/spec-up-t.
    • Click the "Fork" button at the top-right to create a copy under your account (e.g., your-username/spec-up-t).
    • This fork lets you run the workflow without needing write access to the original repo.
  2. Navigate to the Workflow:

    • In your forked repository (e.g., https://github.com/your-username/spec-up-t), go to the Actions tab.
    • Click on the button that says that you understand workflows
    • Find and select the "Create Spec-Up-T Project" workflow in the list on the left.
  3. Start the Workflow:

    • On the right side, you’ll see a "Run workflow" button or dropdown (it might say "Run workflow" directly or be under a small arrow). Click it.
    • A form will pop up with input fields.
  4. Fill in the Inputs:

    • Name of the new project repository:
      • Enter a name for your new project (e.g., my-spec-project).
      • This will be the name of the repository created under your GitHub account (if using a PAT) or the artifact folder (if downloading).
      • Example: my-spec-project
    • Your GitHub username (required if PAT is provided):
      • Enter your GitHub username (e.g., johndoe).
      • Required only if you’re providing a PAT (see below); otherwise, leave blank.
      • Example: johndoe
    • Your GitHub PAT (optional, to push to your own repo):
      • If you want the project pushed to a new repository under your account, enter a Personal Access Token (PAT) here.
      • To create a PAT:
        1. Go to Settings > Developer settings > Personal access tokens > Tokens (classic) in your GitHub account.
        2. Click "Generate new token."
        3. Give it a name (e.g., spec-up-t), set an expiration, and check repo and workflow scopes.
        4. Copy the token (e.g., ghp_xxxxxxxxxxxxxxxxxxxxx) and paste it here.
      • If you leave this blank, the project files will be available as a downloadable ZIP instead.
      • Example: ghp_xxxxxxxxxxxxxxxxxxxxx
  5. Run the Workflow:

    • Click the green "Run workflow" button at the bottom of the form.
    • You’ll be taken back to the Actions page in your fork, where a new run will appear under "Create Spec-Up-T Project via Repo Creation" with a yellow circle (running) or green check (completed). It can take a while (let's say 15 seconds) before the workflow starts, so be patient.
  6. Check the Results:

    • With a PAT:
      • Wait a minute or two for the workflow to finish (refresh the page if needed).
      • Look for a green checkmark next to the run, then click it to view details.
      • In the logs, find the "Output repository URL" step—it’ll show a link like https://github.com/your-username/my-spec-project.
      • Visit that URL to see your new Spec-Up-T project repository!
    • Without a PAT:
      • Wait for the run to complete (green checkmark).
      • Click the run, scroll to the bottom, and find the "Artifacts" section.
      • Download the ZIP file named after your project (e.g., my-spec-project.zip).
      • Unzip it locally or upload it to your own repo manually (e.g., drag files into a new GitHub repo).
info

In the context of GitHub Actions, an ephemeral runner refers to a temporary, single-use virtual machine or container that executes a workflow job and is discarded once the job is complete.

When you start a GitHub Actions Workflow, an “ephemeral runner” is started “in the cloud.” Such a runner is the computer on which the Node.js scripts are run. With one click, everything is done; you, as a user, just have to wait. If you click on the workflow in the middle screen, you can see the console output, so to speak, and get an idea of what is happening.

When you manually trigger a workflow in GitHub Actions (e.g., via the "Run workflow" button on the Actions tab), an ephemeral runner is spun up. The runner downloads the necessary tools, dependencies, and your repository code, executes the defined steps, and then terminates. Because it’s ephemeral, each run starts with a clean slate, ensuring no residual state from previous runs affects the outcome. This is particularly useful for debugging or one-off tasks, as it eliminates concerns about cached data or lingering configurations.

Troubleshooting

  • Error in Logs: If the run fails (red X), click it, expand the steps, and read the error (e.g., "PAT invalid" or "Repo already exists"). Adjust your inputs and retry.
  • No PAT, No Artifact: Ensure the workflow completed successfully—artifacts only appear on success.
  • Repo Not Created: Verify your PAT has repo and workflow scopes and matches your username.
  • No Workflow in Actions: Ensure you’re in your fork’s Actions tab (your-username/spec-up-t), not the original repo.

Example

To create a repo named my-spec-project under johndoe:

  1. Fork trustoverip/spec-up-t to johndoe/spec-up-t.
  2. In johndoe/spec-up-t, go to Actions, select "Create Spec-Up-T Project via Repo Creation," and click "Run workflow."
  3. Inputs:
    • Name: my-spec-project
    • Username: johndoe
    • PAT: ghp_xxxxxxxxxxxxxxxxxxxxx
  4. Result: A new repo at https://github.com/johndoe/my-spec-project.

Enjoy your new Spec-Up-T project—happy specifying!