Workflows

Overview

A workflow is a GitHub Actions workflow file (.github/workflows/*.yml) that defines your CI/CD pipeline. When configured with the Fly action, a workflow becomes the bridge between your code and Fly’s release tracking.

Once configured, every push automatically publishes artifacts to Fly Registry and creates a release with an AI-generated summary, linked PRs, commits, and full traceability – no tokens or secrets needed.

How It Works

Configuration Model

Configuring a workflow means adding two things to the workflow YAML file:

OIDC permissions for secure, token-free authentication:

permissions:
  contents: read
  id-token: write

Fly action to configure package managers on the CI runner:

- name: JFrog Fly - Configure all your package managers to work with Fly registry
  uses: jfrog/fly-action@v1

For Docker, Fly also sets the image path to point to Fly Registry: <your-fly-subdomain>.jfrog.io/docker/my-app:tag

Configuration Status

Each workflow has one of two states:

Configured – The workflow includes the Fly action. It can push and pull artifacts from Fly Registry, creates releases automatically, and has full traceability.

Not Configured – The workflow exists but isn’t using Fly. Artifacts aren’t tracked and no releases are created.

What Happens After Configuration

Once merged, every push that runs the workflow:

1. Authenticates with Fly Registry via OIDC (no tokens needed)
2. Publishes artifacts to Fly Registry
3. Creates a release with AI-generated summary, linked PRs, commits, and artifacts

From Your Coding Agent

The recommended way to configure workflows is through your coding agent. Fly scans your workflow files, generates the changes, and opens a pull request – no manual YAML editing required.

Configure All Workflows

“Configure my workflows with Fly”

Fly scans your .github/workflows/*.yml files and opens a pull request with the required changes. Review, merge, and you’re done.

Configure a Specific Workflow

“Configure this workflow for Fly Registry”

Opens the current workflow file and adds the Fly action and permissions.

Manual Configuration

Add the OIDC permissions block at the top level (after on:, before jobs:) and the Fly action step within your job (after setup steps, before artifact operations).

Full examples →

In Fly Web

Fly Web shows the configuration status of all workflows in each repository, so you can quickly see which workflows are connected to Fly and which still need setup.

Workflow List

Navigate to Git Repositories → select a repository → Workflows tab.

Actions

• Configure Workflow – Opens the coding agent flow or links to manual configuration
• View on GitHub – Opens the workflow file directly on GitHub

Next Steps

• Releases → - What workflows produce
• Developer Workflow → - Full CI/CD configuration guide with examples