Github Actions | Ryan Ositis

Experienced

Cloud-based CI/CD platform for automating builds, testing, and deployment directly from GitHub repositories.

Why I use it

Automation should simplify life, not create new dependencies. I like GitHub Actions because it integrates naturally with GitHub and makes sophisticated deployment workflows surprisingly approachable. Even when an organization isn't ready to adopt it immediately, building a proof of concept can help demonstrate what's possible and guide future modernization efforts.

How I use it

GitHub Actions brings continuous integration and deployment directly into the software development workflow. By defining workflows as code, teams can automatically build applications, run tests, create deployment artifacts, and perform routine operational tasks whenever changes are committed.

During the Caltrans Drupal modernization project, I developed a containerized deployment workflow using GitHub Actions as a proof of concept. The goal was to create a portable, repeatable deployment process that could be executed consistently across environments while reducing manual effort. Although the solution worked well technically, it was ultimately not adopted because the organization did not have staff with the experience needed to maintain the workflow after the project concluded.

For clients, GitHub Actions offers an accessible path toward modern DevOps practices. It reduces repetitive work, improves deployment consistency, and provides a transparent record of how software moves from development into production.

Subscribe to Github Actions