Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add composability/modularization to GH action templates #35

Open
vdice opened this issue Jun 10, 2021 · 1 comment
Open

Add composability/modularization to GH action templates #35

vdice opened this issue Jun 10, 2021 · 1 comment

Comments

@vdice
Copy link
Member

vdice commented Jun 10, 2021

Currently, each supported language has their own set of GH actions. There is a decent amount of shared/duplicated yaml between these.

The goal of this issue is to consolidate common GH action yaml. A couple things to look into:

  1. Consolidating common yaml, perhaps via common templates that all languages can build from
  2. Are there any candidates for creating public GH actions? If so, these can be updated to consume them once available.
@itowlson
Copy link
Contributor

Templates or blocks might be a good initial strategy. Our actions are very much in the pattern of "language determines build, registry determines publish" with the main touchpoint between the two being where to find the assets. So if we could create per-language and per-registry YAML blocks that we could just drop in at substitution time...?

Referencing or creating encapsulated GH actions would also be great - this could help developers putting together workflows by hand, or simplify understanding for devs editing the scaffolded workflows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants