coreos/repo-templates

Perfil de coreos

Última actividad de origen registrada: 1 de julio de 2026 a las 08:44

Catálogo de SkillsMP actualizado: 17 de octubre de 2026 a las 00:09

skills recopiladas: 2

Estrellas en GitHub: 5
Forks en GitHub: 17

README del repositorio

Archivo de origen del README: README.md

Leer el README original

Mostrar README completo

# CoreOS repo templates This repository includes parameterized templates for release checklists used by many different CoreOS repositories. ## Structure of this repo This repo contains [rendering code](tmpl8), some GitHub Actions workflows, and the [Tera templates](https://tera.netlify.app/docs/#templates) and metadata that are rendered and submitted to downstream Git repos. Each Tera template has a adjacent `.yaml` file describing how the template will be applied, and there is also a top-level `config.yaml` tying everything together. Tera templates are rendered with a "context", which is a set of key-value pairs that can be textually substituted into the template and can also affect control flow when rendering it. Context variables are provided via the YAML files. `config.yaml` contains a list of downstream Git repos that we manage and a list of templates that we render. Each Git repo is associated with a short name, which the GitHub Actions workflow expects to match the repo name. `config.yaml` also defines global and repo-specific context variables. Template YAML files contain a list of files, as `(repo, path)` tuples, to be derived from the corresponding template. Repos are referenced by their name in the `config.yaml` repo list. The template YAML also defines template-specific and file-specific context variables. The sources of context variables, from highest to lowest precedence, are: - File-specific `vars` in template YAML - Repo-specific `vars` in `config.yaml` - Global `vars` in template YAML - Global `vars` in `config.yaml` ## Modifying templates To modify templated artifacts: 1. Clone this repo and make your changes locally. Run `make` to compare the resulting rendered files to the versions currently stored in the downstream repositories, or `make output` to generate a complete rendered tree for examination. 2. PR your changes. Reviewers can view the "Render diffs" step of the "Render" CI job to see the changes that will be PRed to the various repos. 3. Merge your changes. CI will automatically submit PRs to affected downstream repos.

Cargando el README del repositorio…

Skills en este repositorio

Desarrolladores de software

1 categorías ocupacionales · 100% clasificado

skill

ocupación

descripción

actualizado

onboard-new-repo

Desarrolladores de software

Add a new downstream repo to config.yaml so it can receive repo-templates

Idioma del texto original: inglés

2026-07-01

enroll-repo-in-template

Desarrolladores de software

Enable an existing Tera template for a downstream repo in the repo-templates system

Idioma del texto original: inglés

2026-04-08

Mostrando 2 de 2 skills recopiladas.

Instalar con un asistente de IA

Copia este prompt en el asistente de IA que estés usando.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/coreos/repo-templates.