Unit 2: Build your factory

Connect an issue backlog

Lesson 220 min

What we’ll cover

Connect a backlog of real issues to your factory to see how it performs under load.

Now that we kicked the tires on our factory, let's start sending some real workloads through it. We'll connect our factory to a backlog of issues, ranging from simple bug reports to larger feature requests.

> new issueimplementpull request
Your factory after this lesson: labeled issues go straight to the builder.

Add your first automation

Let's start by adding our first automation to intake issues. We'll use GitHub to track and label issues, but you're welcome to bring a taskboard of your own as well. Warp Factories supports Linear and Jira out of the box, with webhook support to connect to other services.

  1. Add an issue automation

    Start by creating a new file under automations/ in your factory definition with the convention automations/NAME/automation.md.

    This automation fires when any issue on your repo gets the factory label, and passes on the issue details to your factory. To ensure your factory has access to these issues, be sure to use the organization and repo you're using for your factory (example: my-org/my-markdown-app).

    automations/github-issues/automation.md
    ---
    triggers:
      - provider: github
        event: issue_labeled
        filter:
          repos: [YOUR_GITHUB_ORG/my-markdown-app]
          labels: [factory]
          skip_bots: self
    ---
    Use the issue that triggered this run as the request:
    
    - author: the requester
    - URL: the issue this work tracks; link the pull request on it
    - title / body: the description to follow
  2. Seed the backlog

    Now, let's bring some issues into that backlog. We've created 10 sample issues on the Markdown App template repository that you can copy into your own taskboard.

    Check out your code repository locally (the one that's connected to your factory). Install the dependencies if you haven't already, then run the seed-backlog script. This script copies over those issues into your repository, and applies a new factory label across each of them to kick off the factory automation. Ensure this label matches the label you set up in your automation:

    bash
    pnpm i
    pnpm seed-backlog --label factory
  3. Watch the runs

    Now, head to the "Runs" tab of your factory, and you should see 10 new tasks roar into life. You can track the progress and resulting PRs from here.

    The factory's Runs list showing ten completed runs, each titled after a GitHub issue and linked to its issue and pull request
    One task per labeled issue.
Check your understanding
Say 5 new issues land in the backlog your automation watches. What happens?

Review the output

Once these tasks finish, you can review the output to see how your workers did. Don't merge these changes yet! We'll be revisiting a few of these PRs in the coming lessons.

You can try checking out these branches yourself to see how they behave, and review the pull request descriptions to ensure that static checks ran as expected.

This is great for one-off bug fixes like "add TOML support." But you may have picked up on a few problems for feature requests:

  • What product decisions did the builder "guess" at, instead of requesting human input?
  • What do these changes actually look like (screenshots, recordings, e2e tests)?

We'll address each of these in the coming lessons.