If you are working with Azure DevOps to keep track of your projects, you probably have to deal with sprints. Depending on the length of your sprints, and the fact that you can
Code coverage is an important topic, and a natural step for any developer to explore. In this post we will set up an automatic process using Pester, GitHub Actions and CodeCov to run our tests and visualize the results.
Automate everything is the goal, and this time we take a look at how we can automatically push our PowerShell module to the PowerShell Gallery when creating a new release on GitHub.
Using Pester to run tests on your code, and want that automated when you commit code to your GitHub repository? Me too! Luckily, it's not that hard to set up.
I just recently got into a situation where customer with hybrid Exchange had to change many users SAMAccountName, which led to a whole bunch weird stuff due to hybrid routing addresses. So, quick