// Complete YAML schema reference for File and FileSet resources. Use when writing manifests to manage files (CODEOWNERS, LICENSE, CI workflows, etc.) in one or more repositories, including templating, patches, reconcile modes, delivery method, and import-into behavior.
| name | file-manifest |
| description | Complete YAML schema reference for File and FileSet resources. Use when writing manifests to manage files (CODEOWNERS, LICENSE, CI workflows, etc.) in one or more repositories, including templating, patches, reconcile modes, delivery method, and import-into behavior. |
Use this skill for file-distribution manifests. Keep the main body small and open references only when the request needs them.
File is parsed as a one-repo FileSet internally, but you still author the simpler shapepath and exactly one of content or sourcevia defaults to pushreconcile defaults to additivepatches are applied after template expansionapiVersion: gh-infra/v1
kind: File
metadata:
owner: my-org
name: my-repo
spec:
files:
- path: .github/CODEOWNERS
content: |
* @username
- path: LICENSE
source: ./templates/LICENSE
via: push
commit_message: "ci: sync managed files"
Key fields:
files: requiredvia: push or pull_requestcommit_message, branch, pr_title, pr_body: delivery controlsfiles[].vars: template variablesfiles[].patches: unified diff patchesfiles[].reconcile: additive, authoritative, create_onlyRead these references as needed:
import-into skillUse FileSet to distribute shared files to many repositories.
apiVersion: gh-infra/v1
kind: FileSet
metadata:
owner: my-org # no "name" field
spec:
repositories:
- gomi # simple string
- enhancd
- name: gh-infra # struct with overrides
overrides:
- path: .github/CODEOWNERS
content: |
* @username @co-maintainer
files:
- path: .github/CODEOWNERS
content: |
* @username
- path: LICENSE
source: ./templates/LICENSE
via: push
Each repository entry is either:
name and optional overridesOverrides replace the matching base entry by path for that repository only.
github:// sources are import hard-skips because there is no local write targetFileSet often default to the patch write action in import --intocreate_only affects apply behavior, but import can still update the local master templategh infra validate <path>
gh infra plan <path>
Complete YAML schema reference for Repository and RepositorySet resources. Use when writing or editing manifests for repo settings, labels, actions, branch protection, rulesets, secrets, variables, or repository defaults.
CI/CD integration patterns for gh-infra: auto-apply on merge, scheduled drift detection, self-managed vs central-management layouts, and authentication setup for GitHub Actions workflows.
Overview of gh-infra and command workflow (import, validate, plan, apply). Use when managing GitHub repository settings, labels, actions settings, rulesets, secrets, variables, or files declaratively via YAML manifests.
Use when pulling live GitHub state back into existing gh-infra manifests with `gh infra import --into`, especially for write/patch/skip decisions, shared file sources, template-backed files, and import safety rules.
Use when running demo recordings, diagnosing recording failures, or regenerating GIFs from existing MP4s. Covers the Docker + VHS + ffmpeg pipeline.
Use when creating new VHS demo tapes or editing existing ones. Covers tape syntax, setup scripts, mock-gh data layout, and the checklist for adding a new demo end-to-end.