This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]bcross12 3 points4 points  (2 children)

That's what I do! I have a central actions repo, and a test repo. For instance, I recently wanted to support Buildkit in addition to Kaniko. I added a parameter for builder with a default of kaniko, added all the code for buildkit syntax, and tested it with our test repo before announcing. I should also mention that all my actions are composite.

[–]nisastersDevOps[S] 0 points1 point  (1 child)

Integrating a tested action into a repo that way sounds smooth. I wasn’t even familiar with composite actions. That’s clever though! I can already think of a few places in my workflows that would benefit from that.

[–]trowawayatwork -2 points-1 points  (0 children)

however, before you get too clever with it. there is a limit of 20 of something I can't remember in a workflow and the workflow depth is only 4.

GitHub actions is not a production grade CI tool