fregante/ghat

Allow definition/setup via local template instead of cli

Ouverte

#4 ouverte le 8 nov. 2020

 (2 commentaires) (0 réaction) (0 personne assignée)TypeScript (9 forks)github user discovery
enhancementhelp wanted

Métriques du dépôt

Stars
 (264 étoiles)
Métriques de merge PR
 (Aucune PR mergée en 30 j)

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 env doesn't support arrays for example, and can't be used in strategy.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

Guide contributeur