# Automations

> The repository events that start a Pullfrog run, the default for each, and the progress comment a run posts.

An automation starts a run from a repository event. Each one is a card in the repository console under **Automations**.

| Card | Starts a run when | Default |
| --- | --- | --- |
| [Mentions](https://pullfrog.com/docs/prompts#mentioning-pullfrog) | Someone mentions `@pullfrog` | On |
| [Review PRs](https://pullfrog.com/docs/pr-reviews) | A PR opens, or a draft is marked ready for review | On |
| [Review PRs](https://pullfrog.com/docs/pr-reviews#re-review-on-new-commits) | New commits land on a PR Pullfrog reviewed | On |
| [Enrich issues](https://pullfrog.com/docs/issues) | An issue opens | On |
| [Label issues](https://pullfrog.com/docs/issues#issue-labels) | An issue opens | Off |
| [Address reviews](https://pullfrog.com/docs/addressing-reviews) | Someone reviews a PR Pullfrog opened | On |
| [Fix CI failures](https://pullfrog.com/docs/ci-fixes) | A check suite fails on a PR Pullfrog opened | On |
| [Fix CI failures](https://pullfrog.com/docs/ci-fixes) | A check suite fails on any other open PR | Off |

Each card ends with a [**Custom instructions**](https://pullfrog.com/docs/instructions) field for the runs it starts.

## Outside contributors

On a public repository, three options decide whether someone without write access can start a run. A run they start can reply but cannot push code, and its shell is always [Restricted](https://pullfrog.com/docs/security#shell-environment-scrubbing).

| Card | Option | Default |
| --- | --- | --- |
| Mentions | **Include mentions from non-collaborators** | Off |
| Review PRs | **Include PRs from external contributors** | On |
| Enrich issues | **Include issues from non-collaborators** | On |

## Schedules

A schedule is a [workflow of your own](https://pullfrog.com/docs/custom-workflows) that runs the action on GitHub's `schedule` trigger.

`.github/workflows/weekly-digest.yml`:

```yaml
on:
  schedule:
    - cron: "0 9 * * 1"

jobs:
  digest:
    runs-on: ubuntu-latest
    permissions:
      id-token: write
      contents: read
    steps:
      - uses: actions/checkout@v6
      - uses: pullfrog/pullfrog@v0
        with:
          prompt: Open an issue that summarizes the PRs merged in the last week.
```

## Progress comments

While a run is in progress, Pullfrog posts a temporary "Leaping into action..." comment, updates it with the agent's task list, and deletes it when the run finishes.

![A Leaping into action progress comment during a run](https://pullfrog.com/docs/images/progress-comment.png)

Another tool that reads your PR conversation, such as an LLM-based PR watcher or a bot that mirrors comments, pays for those temporary comments as input. Turn them off under **Automations → General → Progress comments**. Pullfrog posts the first comment before your workflow starts, so only this setting stops it.

| Still posted | Suppressed |
| --- | --- |
| PR reviews, inline comments, and review replies | The initial "Leaping into action..." comment |
| The final result comment, including its collapsible task list | Live task-list updates during the run |
| Plan comments and `@pullfrog` answers | |
| Failure reports, including cancelled and crashed runs | |

The `progress_comments` workflow input suppresses only the live task-list updates:

`.github/workflows/pullfrog.yml`:

```yaml
- uses: pullfrog/pullfrog@v0
  with:
    prompt: ${{ inputs.prompt }}
    progress_comments: disabled
```
