Single responsibility principle

Q: How deeply does GitHub Actions in Action: Continuous integration and delivery for DevOps cover single responsibility principle?

Explains practical boundaries for actions, workflows, and jobs, while treating the principle as guidance rather than an absolute rule.

As explained in GitHub Actions in Action: Continuous integration and delivery for DevOps

The single responsibility principle is a software design principle stating that a component should have one primary responsibility and one reason to change.

The single responsibility principle keeps automation components focused: an action should do one thing well, while a workflow should have a clearly defined goal and reason to run. section 4.6 section 8.4.6

Apply the principle through focused automation boundaries:

Keep shared actions small and avoid Swiss-army-knife interfaces with many inputs and unrelated capabilities. section 4.6
Create workflow files around specific purposes so source or dependency changes affect only the relevant automation. section 8.4.6
Use separate jobs when work must run on different machines; jobs may distribute identical work without defining separate responsibilities. section 8.4.6
Support focused actions with tests, semantic versioning, documentation, clear metadata, and concrete usage examples. section 4.6

Focused workflow organization

Separate automation by goal, use development-cycle events and a branching strategy to trigger the appropriate workflow, and reserve multiple jobs for machine distribution or other justified needs. This reduces maintenance cognitive load and narrows review responsibility, especially where production changes require separation of duties. section 8.4.6

How GitHub Actions in Action: Continuous integration and delivery for DevOps covers it

Cover of GitHub Actions in Action: Continuous integration and delivery for DevOps

liveBook manning.com

Read GitHub Actions in Action: Continuous integration and delivery for DevOps on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Software Design for Python ProgrammersThe Single Responsibility Principle states that a class should have one primary responsibility and remain cohesive around it.
liveBook manning.com

The Art of CodeThe Single Responsibility Principle is an object-oriented design principle stating that a class should have only one reason to change.
liveBook manning.com

Object-Oriented Software Design in C++A design principle stating that a class should have one major responsibility.
liveBook manning.com

.NET MAUI in ActionThe single-responsibility principle is a software design principle stating that a component should have one primary reason to change.
liveBook manning.com

Unit Testing Principles, Practices, and PatternsThe Single Responsibility Principle states that a class or module should have one responsibility and one reason to change.
liveBook manning.com

ASP.NET Core in Action, 3eThe single-responsibility principle is a design principle stating that a class should have responsibility for one piece of functionality and change only when that functionality changes.

Compare how 7 books explain single responsibility principle →

Related concepts

principlekind of · A principle is a general rule, guideline, or value that guides decisions, behavior, or judgments.
cohesive classimplemented by · A class whose methods and instance variables collectively serve one closely related primary responsibility.
SOLID principleskind of · The SOLID principles are five object-oriented software-design principles concerning single responsibility, openness to extension, substitutability, interface segregation, and dependency inversion.
separation of concernsimplements · Separation of concerns is a design principle that organizes a system so distinct responsibilities are handled by separate, independently manageable parts.
functionconfigures · A function is a callable program unit that performs an operation, may accept inputs, and can produce a result or side effect.
pipeline componentimplemented by · A pipeline component is a discrete, executable stage in a data or machine-learning workflow that performs an operation and may consume or produce data artifacts.

This explainer was generated by Manning's knowledge graph from the text of GitHub Actions in Action: Continuous integration and delivery for DevOps. The section links point to the parts of the book it draws on.