APURV
  • Home
  • Journey
  • Projects
  • Blogs
  • Interview
  • Exams
Resume
APURV

Building scalable, secure, and production-ready cloud infrastructure. Automation first.

NAVIGATION

HomeExperienceProjectsCertificationsSkills

TECH STACK

AWSGCPK8sCI/CDLinuxDocker

CONNECT

LinkedInGitHubEmailResume

© 2026 Apurv Gujjar. All rights reserved.
Apurv Gujjar
Apurv GujjarDevOps & Cloud Engineer
|Interview Documentation
Portfolio
Handbooks
🎯Linux🐙Git & GitHub🤖GitHub Actions🌐Networking☁AWS🛠Terraform🐳Docker☸Kubernetes📊Monitoring🛡DevSecOps💰Cost Optimization🚨Incident Scenarios👤HR & Behavioral☁GCP🐍Python
Interview DocumentationGitHub ActionsWhat are Reusable Workflows, and how do they differ from composite actions?
Back to all GitHub Actions questions
Q15

What are Reusable Workflows, and how do they differ from composite actions?

💬Answer

Reusable Workflows allow you to define a complete workflow YAML file in a central repository and call it from other workflow files across multiple repositories (using uses: owner/repo/.github/workflows/reusable.yml@v1).

  • Unlike composite actions, reusable workflows run as independent jobs, can contain multiple jobs, define environment boundaries, and support their own runner configurations.
  • They are triggered using the workflow_call event and accept defined inputs and secrets.

Related GitHub Actions Questions

View All GitHub ActionsQuestions →
Q1

What is GitHub Actions, and how does it process workflows under the hood?

Q2

Can you list and explain the key architectural components of GitHub Actions?

Q3

How do you configure workflow triggers, and what is the syntax for defining manual execution parameters?

Q4

What is a matrix strategy in GitHub Actions, and in what scenarios would you use it?

Apurv Gujjar - DevOps & Cloud Engineer
Created by

Apurv Gujjar

DevOps & Cloud Engineer

Specialized in:DevOpsAWSGCPKubernetesTerraformDocker
View Portfolio