iFlow CLI GitHub Action

Run iFlow CLI commands within GitHub workflows

GitHub Repository

Basic Usage

Using the action in your GitHub workflow is simple:

- name: Run iFlow CLI
  uses: iflow-ai/iflow-cli-action@v2.0.0
  with:
    prompt: "Analyze this codebase"
    api_key: ${{ secrets.IFLOW_API_KEY }}

Getting Started

1. Add iFlow API key to your GitHub repository secrets as `IFLOW_API_KEY`
2. Create a workflow file in your `.github/workflows/` directory
3. Reference the action with your desired prompt
4. Customize inputs as needed for your use case

Issue Triage Workflow

name: '🏷️ iFLOW CLI Automated Issue Triage'

on:
  issues:
    types: [opened, reopened]
    
jobs:
  triage-issue:
    runs-on: 'ubuntu-latest'
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4

      - name: 'Run iFlow CLI Issue Triage'
        uses: iflow-ai/iflow-cli-action@v2.0.0
        with:
          api_key: ${{ secrets.IFLOW_API_KEY }}
          prompt: |
            Triage the following issue:
            Issue Title: "${{ github.event.issue.title }}"
            Issue Body: "${{ github.event.issue.body }}"

Required Inputs

• prompt - The prompt to execute with iFlow CLI
• api_key - iFlow API key for authentication

Optional Inputs

• base_url - Custom base URL for iFlow API
• model - Model name to use (default: `qwen3-coder-plus`)
• timeout - Execution timeout in seconds
• precmd - Shell commands to execute before iFlow CLI

Outputs

• result - Output from iFlow CLI execution
• exit_code - Exit code from iFlow CLI execution

Pre-Execution Commands

precmd: |
  npm install
  git fetch origin main

Custom Settings JSON

settings_json: |
  {
    "theme": "Dark",
    "selectedAuthType": "iflow",
    "apiKey": "${{ secrets.IFLOW_API_KEY }}",
    "baseUrl": "https://custom-api.example.com/v1"
  }

MCP Server Integration

Connect to external tools and services using Model Context Protocol

iFlow CLI GitHub Action

Enhance your GitHub workflows with AI-powered automation

"Leverage the power of AI to automate your development workflows"