Git is a powerful version control system, which has fast become the industry standard for developers around the world.
Recently, whilst working with Git on the Windows OS I encountered the error Filename too long. In this post, I’ll delve into the root cause of this error and provide the solution that worked for me.
In 2024, GitHub announced that GitHub Certifications were generally available, offering a means to demonstrate knowledge and experience on the GitHub platform.
Having recently completed the GitHub Actions Certification, in this blog article I share my experience of sitting the exam, including, my study approach, the learning resources I used, tips for the exam, a useful mindmap containing key concepts, and much more!
Recently whilst working on a C# solution in Visual Studio 2022, I encountered an unusual issue whereby VS would fail to build my project according to the build log, however, VS did not report any errors in the “Error List” panel.
If you too have encountered the same error, then you are in luck, because I’ll explain the solution that worked for me.
Recently whilst trying to enable GitHub CoPilot within VSCode in a corporate enterprise environment, I encountered the following warning when trying to authenticate with GitHub:
[certificates] failed to read root certificates
Often in a corporate enterprise IT environment, IT will install a self-signed root certificate, which all devices must trust before they can access the internet via a central proxy server. This was indeed the case in my situation. However, the above error message indicated that VS Code didn’t recognise or trust this self-signed certificate, preventing it from properly authenticating with GitHub.
Recently, whilst trying to run the following command in a GitHub Actions workflow script to create a new Release in my GitHub Repository:
gh release create XXXX --generate-notesHowever, strangely I encountered the following workflow error:
HTTP 403: Resource not accessible by integrationIf you’ve faced the same error, then you’re in luck – because I’ll be sharing the solution that worked for me to resolve this issue.
Continue readingRecently whilst using Cmder on Windows 11, I encountered the below error while running command ‘ls’ to list the files, and in this post I’ll explain the solution that worked for me.
‘ls’ is not recognized as an internal or external command, operable program or batch file.
Whilst recently installing Specflow on a new Windows PC, I ran into an unexpected error after running the below command:
dotnet tool install --global SpecFlow.Plus.License --version 3.9.7This is the error I encountered whilst running the above command:
C:\Users\XXXX\AppData\Local\Temp\cd1e38b3-c92a-436d-b439-f1535d848adc\restore.csproj : error NU1101: Unable to find package specflow.plus.license. No packages exist with this id in source(s): C:\Program Files\dotnet\library-packs, Microsoft Visual Studio Offline Packages The tool package could not be restored.
Tool ‘specflow.plus.license’ failed to install. This failure may have been caused by:
You are attempting to install a preview release and did not use the –version option to specify the version.
A package by this name was found, but it was not a .NET tool.
The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
You mistyped the name of the tool.
For more reasons, including package naming enforcement, visit https://aka.ms/failure-installing-tool
Deploying resources to the cloud through deployment pipelines requires the need to authenticate with the various cloud providers in a standardised and secure manner. GitHub Actions offers the ability to authenticate with Azure using OpenID Connect (OIDC).
In this post, I’ll guide you through the process of setting up OpenID Connect (OIDC) authentication with Azure and GitHub Actions.
SharePoint Framework (SPFx) offers a flexible approach to building custom solutions for Microsoft SharePoint that leverage modern web development technologies.
Recently whilst deploying a SharePoint Framework (SPFx) solution into a SharePoint Online environment, I encountered intermittent caching issues and 404 failures. There was no clear pattern as to why the issues would occur. After staring at the code and pulling my hair out, I eventually came across a solution…
In this post, I’ll be sharing the solution that worked for me.
Azure Function Apps allow developers to build and deploy event-driven applications in the cloud. However, as with any software we can sometimes run into unusual issues, in particular, I recently ran into the below error when trying to deploy an Azure Function App through a GitHub Actions CICD pipeline.
If you have also encountered this issue, then you are in luck, because in this article we’ll explore the cause of this error and how I solved the issue.
Continue reading“Internal Server Error (CODE: 500)”
“There is not enough space on the disk.”
© 2025 Shane Bartholomeusz
Theme by Anders Noren — Up ↑
