CI/CD Reference

Technical reference for running Agenda Panda inside CI/CD pipelines.

Looking for the acquisition-style walkthrough first? Start with the public CI/CD guide.

Quick Start

1. Create an API key in Settings
2. Add it as a secret (AP_API_KEY) in your CI system
3. Use the GitHub Action or raw CLI
4. Pass --project and --connection explicitly when your automation should not depend on mutable local defaults

GitHub Action

- uses: agendapanda/post-action@v1
  with:
    api-key: ${{ secrets.AP_API_KEY }}
    content: "We just shipped v2.0!"

Raw CLI (any CI system)

curl -fsSL https://agendapanda.com/install.sh | bash
AP_API_KEY=$AP_API_KEY ap post "Deployed to production" --project "$AP_PROJECT" --connection linkedin

Calendar sync in automation

Keep a calendar.json in your repo and sync on every push:

- uses: agendapanda/post-action@v1
  with:
    api-key: ${{ secrets.AP_API_KEY }}
    calendar-file: "./calendar.json"

With raw CLI commands:

curl -fsSL https://agendapanda.com/install.sh | bash
AP_API_KEY=$AP_API_KEY ap calendar sync --file calendar.json --project "$AP_PROJECT" --dry-run
AP_API_KEY=$AP_API_KEY ap calendar sync --file calendar.json --project "$AP_PROJECT" --delete-missing

See the Calendar as Code guide for the JSON format.

Release Packets via GitHub App

Release packets are now created through the GitHub App integration, not through a repo-local GitHub Actions workflow. Use GitHub App when the job is GitHub release published -> create a review-ready launch packet.

Recommended setup

1. Open Data Sources in Agenda Panda.
2. Connect the GitHub App.
3. Select the repos you want Agenda Panda to monitor.
4. Publish a GitHub Release in one of those repos.
5. Review the generated packet in Agenda Panda before publishing any artifacts.

Why this replaced the workflow path

• No repo-local YAML file to install or maintain
• No repository secrets like AP_API_KEY or AP_PROJECT_ID needed for packet generation
• Clear attribution in the product: packet created by the GitHub App, not by an internal CI job
• Better product fit for engineering teams connecting multiple repos over time

What this guide still covers

This CI/CD guide is still the right reference for:

• posting directly from CI with the GitHub Action
• running the CLI in GitHub Actions, GitLab CI, or other pipelines
• syncing a calendar file from git into Agenda Panda