gitops

Automate TrueFoundry deployments via GitOps pipelines using tfy apply.

13|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/truefoundry/tfy-agent-skills --skill gitops-truefoundry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitops
Source: https://github.com/truefoundry/tfy-agent-skills/tree/main/skills/gitops
Command: npx skills add https://github.com/truefoundry/tfy-agent-skills --skill gitops-truefoundry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill automates the deployment of your applications and infrastructure to TrueFoundry by treating your Git repository as the single source of truth, enabling robust CI/CD pipelines.

Core Features & Use Cases

  • GitOps Workflow: Store TrueFoundry resource configurations (YAML specs) in Git.
  • CI/CD Integration: Set up automated deployments via GitHub Actions, GitLab CI, or Bitbucket Pipelines.
  • Pull Request Validation: Automatically validate deployment specs using tfy apply --dry-run on pull requests.
  • Automated Deployment: Deploy changes automatically when merged to your main branch.
  • Use Case: You want to ensure that every time a new version of your API's configuration is merged into the main branch, it's automatically deployed to your staging environment after passing validation checks in a pull request.

Quick Start

Use the gitops skill to set up a GitHub Actions workflow for validating your TrueFoundry YAML specs on pull requests.

Frequently Asked Questions about gitops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate deployments using GitOps and infrastructure as code?

GitOps automates deployments by treating your Git repository as the single source of truth for infrastructure as code. You store deployment configurations in Git, and merging changes to the main branch automatically triggers CI/CD pipeline deployments to your target environment.

Can I use GitHub Actions or GitLab CI for TrueFoundry deployment pipelines?

Yes, you can use GitHub Actions, GitLab CI, or Bitbucket Pipelines for TrueFoundry deployment pipelines. These CI/CD integrations automate validation and deployment workflows directly from your Git repository whenever new changes are merged.

How do I validate TrueFoundry YAML specs on a pull request?

You validate TrueFoundry YAML specs on a pull request by running an automated dry-run validation check within your CI/CD pipeline. This ensures deployment configurations are valid and error-free before they are merged into the main branch.

What is the best way to manage infrastructure as code for automated CI/CD?

The best way to manage infrastructure as code for automated CI/CD is storing your resource configurations as YAML specs in Git. This GitOps approach ensures every deployment is version-controlled, validated via pull requests, and automatically applied upon merging.

Do I need to store TrueFoundry deployment configurations in Git to use GitOps?

Yes, storing TrueFoundry deployment configurations in Git is required for GitOps. This practice establishes the Git repository as the single source of truth, enabling automated validation on pull requests and seamless deployments when changes are merged.