Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Mastering GitHub Actions

You're reading from  Mastering GitHub Actions

Product type Book
Published in Mar 2024
Publisher Packt
ISBN-13 9781805128625
Pages 490 pages
Edition 1st Edition
Languages
Concepts
Author (1):
Eric Chapman Eric Chapman
Profile icon Eric Chapman

Table of Contents (22) Chapters

Preface 1. Part 1:Centralized Workflows to Assist with Governance
2. Chapter 1: An Overview of GitHub and GitHub Actions 3. Chapter 2: Exploring Workflows 4. Chapter 3: Deep Dive into Reusable Workflows and Composite Actions 5. Chapter 4: Workflow Personalization Using GitHub Apps 6. Chapter 5: Utilizing Starter Workflows in Your Team 7. Part 2: Implementing Advanced Patterns within Actions
8. Chapter 6: Using HashiCorp Vault in GitHub 9. Chapter 7: Deploying to Azure Using OpenID Connect 10. Chapter 8: Working with Checks 11. Chapter 9: Annotating Code with Actions 12. Chapter 10: Advancing with Event-Driven Workflows 13. Chapter 11: Setting Up Self-Hosted Runners 14. Part 3: Best Practices, Patterns, Tricks, and Tips Toolkit
15. Chapter 12: The Crawler Pattern 16. Chapter 13: The Configuration Centralization Pattern 17. Chapter 14: Using Remote Workflows to Kickstart Your Products 18. Chapter 15: Housekeeping Tips for Your Organization 19. Chapter 16: Handy Workflows for Managing Your Software 20. Index 21. Other Books You May Enjoy

Workflow structuring and good habits

Structuring your GitHub Actions workflows and establishing good habits early on is critical for ensuring maintainability, readability, and efficiency. Here are some best practices:

  • Keep workflows focused and concise: It can be tempting to make a single workflow handle many aspects of your CI/CD process, but this can lead to workflows that are complex, hard to maintain, and difficult to understand.

    Instead, each workflow should have a single, clear purpose. For example, one workflow might be responsible for linting and running tests whenever code is pushed. Another workflow could handle deploying your application to a staging environment when a pull request is merged. This division of responsibilities makes it easier to understand the role of each workflow, simplifies troubleshooting when things go wrong, and allows for more flexible customization since changes in one workflow won’t affect others. It also allows you to take advantage...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}