• EXECUTION
  • STATUS
  • REPORTS
  • HUMAN

How to trigger CI/CD workflows with your AI

Connect Forgejo to your agent to manage builds through chat. You'll trigger specific Actions workflows without leaving your interface.

Ask AI about this page

Short answer

Can I start Forgejo Actions from my AI chat?

Yes. You tell your agent which repository and workflow to run, and it sends the command to Forgejo. You'll see the results of that request immediately.

The outcomes of your request.

What happens when you trigger a build

Your agent handles the communication with Forgejo so you don't have to.

EXECUTION

Active builds

The agent uses dispatch_workflow to start a specific Action. You get a confirmation that the process is running.

STATUS

Build tracking

Your agent can check the state of your workflows. You'll know if a build is pending, running, or finished.

REPORTS

Success or failure

The agent relays the outcome of the run. You'll see if the pipeline passed or if it hit an error.

HUMAN

Manual code edits

The AI cannot change your YAML files or repository settings. You still handle all code and configuration changes yourself.

The workflow

What your AI does when you request a build.

The agent translates your request into a direct command for Forgejo.

  1. Locate the workflow

    Your agent identifies the specific repository and the workflow file you want to run based on your message.

    dispatch_workflow
  2. Trigger the Action

    The agent sends the trigger command to Forgejo to start the build process.

    dispatch_workflow
  3. Verify the start

    The agent checks that Forgejo received the request and successfully queued the job.

    dispatch_workflow
  4. Report status

    The agent tells you that the workflow is active and ready for you to monitor.

    dispatch_workflow

Try it

Copy these to start.

Use these prompts to run your first build.

Starting points

Replace the repo names and workflow filenames with your own project details.

Forgejo Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_OGbMMQVsinb0BjKH6qJI5Qwlr4pWGYjZRMU7QWs7/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Forgejo capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "forgejo-gitea-fork-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_OGbMMQVsinb0BjKH6qJI5Qwlr4pWGYjZRMU7QWs7/mcp"
    }
  }
}
Copy into chat04
  • Trigger the 'deploy.yml' workflow in the 'web-app' repo.

  • Run the CI build for my 'api-service' repository.

  • Start the 'test-suite' workflow in the 'data-processor' repo.

  • Kick off the production deployment workflow for 'frontend-client'.

  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Start here

Connect Forgejo once, then ask.

Link your Forgejo instance to Vinkius. Your credentials stay encrypted, and you can start running builds immediately.

Connect Forgejo to your AI

FAQ

How the Forgejo Connector behaves

  • 01

    Can the AI edit my workflow files?

    No. The AI can only trigger existing workflows. You must edit your YAML files manually.

  • 02

    Can the AI delete my repositories?

    No. This Connector is limited to triggering workflows.

  • 03

    Does the AI need my Forgejo password?

    No. You connect via Vinkius, and your login details are kept secure and encrypted.

  • 04

    Can I pass inputs to the workflow?

    Yes. If your Forgejo Action is set up to accept inputs, the AI can include them in the request.

  • 05

    Can the AI see my private code?

    The AI only accesses the specific data needed to trigger the workflows you request.

  • More questions about Forgejo? The Connector page answers them. See everything the Forgejo Connector can do

Connect Forgejo to Claude, Cursor, ChatGPT & more