DevOps

You’ve heard of GitHub. You’ve heard of GitHub Actions. You’ve heard of Azure. But how can GitHub Actions help you deploy your workloads to Azure? In this demo-filled, action-packed session, we will Introduce GitHub and GitHub Actions, Cover the fundamentals on what you need to know to build a GitHub Action Workflow, Identify resources that you can use to continue your journey in using GitHub Actions to deploy to Azure

ToolUp Days is all about showing the thought process and decisions made when creating an application. Join Chris and Matt as they build a new application from the ground up, including development processes, tooling, service choices and architectural decisions!

You may be familiar with GitHub for your own Open Source (OSS) projects. But, did you know that you can use those same practices internally for your end-to-end development using GitHub Enterprise? Join Chris for a whistle-stop tour into GitHub Codespaces, GitHub Actions, GitHub Copilot and how you can bring DevSecOps best practices into your day-to-day work!

Technical discussion on how to automate and maintain custom RBAC role definitions in Azure using GitHub actions.

ToolUp Days is all about showing the thought process and decisions made when creating an application. Join Chris and Matt as they build a new application from the ground up, including development processes, tooling, service choices and architectural decisions!

A new phenomenon stand out in recent years: security must pervade the entire software development lifecycle. Except it isn’t. Current generation of processes and tools is lacking crucial features to properly manage modern security risks. Think of the Log4J event. Were you able to identify all affected components? Were they internally developed, or you need a vendor support? How fast you were able to deliver a fix? In this talk we’ll explore the challenges, what you can do with current tools, and which gaps should be addressed by communities through better practices and new tools.

What separates the highly-skilled developer from the one fresh out of college? Why is it that some developer’s code is far easier to maintain and others are nearly impossible to decipher? Both boil down fundamentally to whether you can easily understand the ideas and intent conveyed in their code. So what makes for easily understood code? There are some communication principles we can apply to our code to make it cheaper to change, and faster to understand. After all Code is read more often than it is written. It ought to be easy to read!

Chris joins Mert Yeter on Mert to the future show demonstrating how GitHub has some amazing capabilities beyond repositories! GitHub Projects, GitHub Copilot, GitHub Codespaces, GitHub Actions and more! Tune in to find out!

In a couple of previous blog posts, I provided a writeup on the GitHub Projects Beta. I wrote two posts on automation within GitHub Projects (Adding Issues to GitHub Projects with GitHub Actions for a user profile and Adding Issues to GitHub Projects with GitHub Actions for an Organization profile). I’m pleased to say that the capabilities went Generally Available last week! As a result of the GA announcement and resulting changes, I need to post updates to my older samples.

GitHub is one of my passion areas. You may have realised that already, with the amount of content that I’ve written about it. That’s only going to continue, because I’ve recently been hired there as an Enterprise Advocate. I’ve been supporting customers in their DevOps journey for the past 9 years or so. Interestingly, there are some reoccurring themes that I’ve found that are common. One of those themes is that DevOps is an App Development concept. In fact, it’s something that can be applied across domains (e.g. Infrastructure, Data, etc.) This is the start of a new blog series that will address those common themes, particularly in the context of GitHub.