You have a working set of GitHub actions, but several environments that you want to deploy into. How do you easily separate secrets for use between environments, and ensure you have approvals before releasing into production? For that, you’ll need to use Environments! We’ll explore those in this episode of Cloud with Chris!
For some time, I’ve been using GitHub actions to update the content of my site (i.e. pages, descriptions, metadata, etc.). Through Hugo, these content updates automatically update the RSS feeds. This then makes the episodes appear in podcast services such as Apple Podcasts, Google Podcasts and Spotify. However, throughout that time I have been manually uploading the podcast files to my storage account. It wasn’t a significant overhead, but I kept thinking that there must be a better way to do this. And, there is - I’ve implemented it! This blog post will walk you through why I’ve made these changes, how I made them and what the result is.
I’ve talked in the past about my Open Source journey, and some of the contributions that I have made in the community. In my current role, I’ve been leading on the global strategy for my team’s DevOps practice, defining the areas of focus and initiatives that may be beneficial for the team. In this post, I’m going to talk through one of these initiatives, and how you can contribute towards the Azure GitHub Actions experience!
In this episode, we’re going to be taking a slight detour away from GitHub actions and focus on some of the announcements from GitHub universe last week. We’re going to explore them both from the announcements, and also take a look at some of those features that have already been released. Stay tuned!