Home

Dependencies Between Workflows in GitHub Actions

Introduction

GitHub Actions is an advanced automation platform designed to help developers streamline their CI/CD pipelines efficiently. One of its standout features is the ability to create interdependent workflows, which significantly enhances the automation capabilities and flexibility of your development processes.

This wiki, along with the associated code repository, delves into 10 practical scenarios that illustrate various methods for managing workflow dependencies in GitHub Actions. Each scenario provides a comprehensive example and step-by-step guidance to help you implement and understand these dependencies effectively. You can find the complete implementation details in the underlying repository.

Table of Contents

1. Manual Workflow Launch
2. Reusable Workflow (Simple Example)
3. Reusable Workflow with Inputs and Secrets
4. Using Outputs from Reusable Workflow
5. Nesting Reusable Workflows
6. Composite Actions
7. Sequential Workflows (Simple Example)
8. Sequential Workflows Based on Conclusion
9. Using Data from Triggering Workflow
10. Branch-Based Workflow Execution

Overview

This wiki is structured to provide a step-by-step guide for each scenario. Each page will cover:

• Use Case: A brief description of the scenario and its applications.
• Implementation: Detailed implementation steps with YAML code examples.
• Instructions: How to run and test the workflows.

By following these examples, you can leverage the full power of GitHub Actions to create complex, dependent workflows that streamline your CI/CD processes.

Getting Started

To get started, navigate to the specific scenario you are interested in from the Table of Contents above. Each page will guide you through the setup and execution of the workflow.

For any questions or contributions, please visit the github-workflow-dependencies-demo repository.