Hands-On CI: Building Your First GitHub Actions Workflow
We have previously talked about why Continuous Integration is a powerful DevOps concept for helping your team develop high-quality code faster. Today we are taking you through a deep-dive into the “how,” with step-by-step instructions for setting up a linting pipeline in GitHub Actions. We’ll explain how and why CI workflows can take your team to the next level!
Why Your Team Needs pre-commit
It’s easy to overlook pre-commit when you’re already using GitHub and have a continuous integration pipeline. Why add complexity? In fact, when used well, pre-commit can be the simplest and most effective way to eliminate bugs, style issues, and config drift before they even enter your Git history. pre-commit helps shift quality left, right into your fingertips as you write and commit code.
The Goldilocks Pull Request
A Pull Request should be focused. It should do one thing well: fix a bug, add a feature, or refactor a specific part of the code. This helps reviewers follow what changed and why, help CI tools test your changes, and help your future self understand the changes. Your PR should appeal to Goldilocks: not too large, and not too small.
How Code Reviews Should Work
The best code reviews feel like collaboration, not judgment. They’re an opportunity to ask questions, learn, and improve as a team. When the small stuff is already taken care of, there’s space for that conversation to happen. Caparra is building tools to make this easier for your team.
Python Linter Showdown
Python Linter Showdown! It’s time for a spirited comparison of four popular Python linters: black, flake8, pylint, and ruff. Each tool promises to tidy up your code, catch pesky bugs, and keep your scripts neat. Our contestants today will face off on three files containing some not-so-great Python. Get ready to witness our code-based house of horror!