Rob's Blog

I notice a lot of people getting lost in their GitHub notifications.

This one took me some time to figure out, so I wanted to have something for the next time I need it :-).

I have a nice working from home setup that allows me to use a great camera, lights and microphone.

There is a lot of confusion of what GitHub (access) tokens are and how you should use them for automating things inside of GitHub.

At my customer we have the need to create a lot of GitHub Apps.

I’ve been discussing using GitHub Actions in a secure way for a while now (see here), and I got a question on how to improve your usage of actions.

This post is for sharing my dev.to entry for the 2021 GitHub Actions Hackathon.

I keep coming across files in GitHub that have some mystic magic feeling to them.

My session on GitHub Universe is now available here.

One of the best practices of using GitHub Actions is to fork all actions that you want to use to your internal actions organization.

You can create GitHub Actions running in a container, which allows you to execute ‘anything’ in an action that can be run inside a container, including PowerShell, my favorite scripting language.

I am an avid PowerShell user and have been using it for a while now.

If you need to host your own GitHub Actions runners that will execute your workflow, you have multiple options: you can go the traditional route and host them on your own VM’s.

Sometimes you spot interesting things online that you have to figure out 😎.

Today I got to deliver my session “Using GitHub Actions Securely” at the Solidify show, hosted by our friends at Solidify.

This one took me way to many trials and searches to figure out, so I wanted to store it here in case I need it later on.

Today I got to deliver my session “Using GitHub Actions Securely” at Techorama, my favorite conference.

Often you come across an organization that has a policy to use self signed certificates on internal services: as long as you control the workstations used to connect to them, that is a solution that might work.

I got some questions recently on my office setup at home, so it might be helpful to share it here as well.

Ever since Microsoft acquired GitHub we have been looking at how this will play out in the long run with their Azure DevOps offering.

Coming from years of Windows dev experience to using a Bash shell took a while to know some of the differences between the two.

I was building a new GitHub Action today with a Dockerfile and got a strange error… `unable to prepare context: path “/action” not found.

One important best practice for any Continuous Integration / Continuous Deployment setup is thinking about attack vectors for your setup.

Small tidbit so I could potentially find this later on: If you are running SonarQube yourself with the Community Edition (for a POC for example, otherwise invest in yourself by getting a higher edition!)

In this post I want to look into Private Runners for your GitHub Workflows and show you some best practices for them.

I’ve been diving into the security aspects of using GitHub Actions and wanted to share some best practices in one place.

I’ve been diving into the security aspects of using GitHub Actions and wanted to share some best practices in one place.

Today I delivered my GitHub Actions & Security session at NDC London for the first time (both for the session and NDC London 😁).

I wanted to use the GitHub Container Registry to host an image for me and had some issues setting things up.

If you have proper source control in place, you have a central location that holds the source code.

I was thinking about the teams I’ve been helping out in my professional work life and suddenly noticed that there seem to be different stages that each team goes through in an effort to improve something in their day-to-day work.

One of the first things to get in order when improving your DevOps way of working is having proper version control of your source code.

If you have a good Continuous Integration process in place, you can start using the generated artefact to deploy that to an environment as the next state of enlightenment in your DevOps way of working.

Alt. title: approval to an environment blocks the whole pipeline Sometimes you find out about something and feel rather stupid.

Recently I got asked if you could use GitHub Actions to deploy to an IIS web application which of course I had to test :grin:.

Sometimes you have these weird things you run into, and I’m sure I will not be able to find this one if I don’t store it here.

While building up a scheduled pipeline for updating our NuGet dependencies I found NuKeeper to help with automatically updating the packages we use.

Today I ran into an issue that I tried to clone a Git repository with large filenames/folder paths in it. fatal: cannot create directory at 'src/Modules/<long path here>': Filename too long warning: Clone succeeded, but checkout failed.

I had an issue running an EntityFramework command after updating the NuGet packages to the latest version and searching got me to multiple steps and sites to get things fixed.

Today I encountered an issue while interacting with the Azure DevOps API.

Today I got asked how you could register a Startup and/or Shutdown script on Windows through PowerShell.

Today someone in the Azure DevOps Club slack asked a question about finding the repo from the default wiki in Azure DevOps.

Today I faced an issue with Azure Active Directory authentication that was interesting enough to not this down for later reference 😁.

I want to target .NET Standard so I can always use my libraries in any project later on, independently of its target framework (as long as it supports the .NET Standard version I’m targeting). unsplash-logoPhoto by Hans Vivek Today I had an issue with usi…

In Azure DevOps I needed to determine a variable in one deployment stage, and use it in another.

Sometimes you want to log information during the startup of the web application.

Sometimes you need to run the Azure DevOps Agent behind a proxy.

I was working on a new .NET Core Unit/Integration Test project in a solution using Visual Studio and need to load some setting from the configuration.

Sometimes you need to deploy an application on a machine, but there is no option to use PowerShell remoting from the outside.

We’ve all been there, what happens when you commit changes to the master branch and during the sync to the remote you get an error.