Reuse/import workflows
See original GitHub issueDescribe the enhancement
Workflows tend to grow large once you start splitting some steps to run in separate jobs. Some other workflows are inherently large because they do a lot.
In many cases, I reuse the same workflow in multiple repositories and I wish I could just import it instead of copy-pasting it and manually updating it everywhere.
Code Snippet
I wish I could just use this in a workflow file:
import:
- use: fregante/workflows@v1
file: webextension-deployment.yml
and this would work as if I copied the whole file.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:45
- Comments:8
Top Results From Across the Web
Reusing workflows
You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow. Reusing workflows avoids duplication. This...
Read more >How to start using reusable workflows with GitHub Actions
Reusable workflows offer a simple and powerful way to avoid copying and pasting workflows across your repositories.
Read more >Guidelines for Importing Reusable Workflows
If you import a reusable workflow by using the Import Reusable SharePoint 2010 Workflow template, you can run or change the solution just...
Read more >Avoid Duplication! GitHub Actions Reusable Workflows
Reusable Workflows extend this concept, allowing you to reference an entire workflow in another one. If Composite Actions can be thought of as ......
Read more >Reuse portion of github action across jobs
A reusable workflow can define outputs that extract outputs/outcomes from executed steps. They can be easily used to pass data to the "main" ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The biggest reason I’m currently staying on Travis CI for existing projects is that the same config for GitHub Actions is more verbose and boilerplaty. Would be nice if workflows could be reused across repos.
I ended up writing my own tool to store my workflows in a repo and easily download/update them elsewhere:
https://github.com/fregante/ghat