fregante/ghat
Allow definition/setup via local template instead of cli
Aberta
#4 aberto em 8 de nov. de 2020
enhancementhelp wanted
Métricas do repositório
- Stars
- (264 estrelas)
- Métricas de merge de PR
- (Nenhuma PRs mesclada em 30d)
Description
Currently the only customization possible is via the global env property, but unfortunately this isn't available everywhere in the workflow and can't be used to customize a workflow template.
I foresee a few ways to reuse existing templates:
Plain merging of a local template (e.g. .github/workflows-ghat/ci.yml) with the remote template
# Fetch template
apply: fregante/ghat/templates/node
# Overwrite existing `on` property with
on:
- push
Importing single jobs
on:
- push
jobs:
test:
name: Let's test stuff
apply: fregante/ghat/templates/node#jobs.test # It would only merge the specific jobs.test section
build:
needs: test
steps:
- run: echo My other steps
An advanced way to customize the templates
For example it could apply some ENVs at merge time like GitHub does with the $default-branch variable:
- because
envdoesn't support arrays for example, and can't be used instrategy.matrix - some conditions could be pre-evaluated, so that whole steps/jobs could be dropped/added at merge time instead of just being silenced at run time.
Initially defined in https://github.com/sindresorhus/project-ideas/issues/128