GitHub Actions Workflows can provide a great abstraction layer for creating or orchestrating build and release processes. Since we're running code -- in some cases, from third-parties -- it's important to understand how to secure the environment from malicious Actions. This is where permissions can help.

Java makes it surprisingly easy to manage and package complex projects using Apache Maven. One question I'm frequently asked -- how does this integrate with GitHub Actions? Turns out that the answer is "surprisingly well!"

Git has some interesting behaviors built into it. For example, it makes it easy to squash a set of commits into a single commit. This creates a very simple history. But what happens if that history that you're eliminating has a tag applied to it? Does that tag get eliminated? Does it point to the newly squashed commit? Today's article explores what to expect in that situation … and why.

It can sometimes be challenging to understand how branches work with the process of triggering Actions workflows in GitHub. Can you have a workflow per-branch? What about child branches? Plan your strategy with confidence by learning when the Actions workflow will run.

Probot makes it simple to create GitHub Apps, but sometimes the APIs update faster than Probot does. Learn how you can implement unsupported web hooks and APIs.