Ken Muse

If you can code it, someone will find a way to exploit it ( accidentally or intentionally). Anytime development efforts are involved, it’s important to minimize security risks and bugs. This is also true with GitHub Actions, which allows you to script advanced automation solutions. Because of this, it’s important to understand where injection can occur and how to avoid it.

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.

In previous articles, we’ve explored the costs for inefficiencies in the development practice. What about the human costs associated with needing to hire and retain top talent? These costs are easily overlooked and rarely included. In this post, we’ll explore the costs associated with replacing lost team members and how top recruiters can help to minimize these expenses.

What if I told you that the portal experience you see with the Microsoft-provided resources was also available for your resources? Want to build a nice wizard for your ARM template? It’s time to dive deeper into Azure and learn how to develop ARM and Bicep templates like a pro. Learn to create your own custom Azure Portal experience!