From GitHub to NuGet

My first package on


Ankit Vijay

3 years ago | 5 min read

Original Post:

I have been contributing to open source for quite some time. However, with some exceptions, most of these contributions had been small, intending to solve a particular problem at my workplace.

In addition to this, none of my previous contributions went beyond a public repository on my GitHub account. But I was keen to change that and a small vacation during Covid-19 turned out to be perfect timing.


Stay-at-home vacation during Covid-19 allowed me to do something I wanted to for a long time, that is, developing a NuGet package that can be used by hundreds of developers across the globe.

In this post, I have described my journey from creating a repository in GitHub to publishing the package on I hope this encourages some of you to do something beyond your usual work.

The selection criteria

What to build turned out to be a task in itself. Here are some of the things I was looking to achieve from this entire exercise:

  • The project should be small and simple that I could complete within 8-10 person-hours. I had no intention of spending my entire vacation on this
  • There should not be any dependency on a 3rd party library.
  • Despite being simple, it should solve some “real” developer problems.
  • The project should tick all the boxes of a “typical” open source project such as a GitHub repository, unit/ integration tests, an automated build pipeline, and the ability to publish the package to NuGet.
  • It should come with the documentation/ instructions on how the Nuget package can be consumed.
  • It should be easy to maintain and accept contributions from the community.
  • Last, but not least it should provide a template for several other NuGet packages which I may publish in the future.

The problem statement

With the above points in mind, I decided to create a middleware that returns an exception as a JSON response for an ASP.NET Core Web API. This is a problem I have faced several times at my workplace.

The default ASP.NET Core template comes up with the middleware, UseDeveloperExceptionPage, which returns the exception in the form of HTML or plain text. However, many times this is not sufficient and developers want to consume a JSON response instead. I could not find an official or well-received 3rd-party package that solves this problem at present.

GitHub Repository

As a first step, I created an empty repository. After several attempts, I settled for the name DeveloperExceptionJsonResponse for my GitHub repo and eventually the NuGet package (Naming is hard).

Next, I used to create a .gitignore file for my repository. If you have not heard of this, it is a great tool to auto-generate the gitignore files for your projects.

To start with, I decided to go with GitHub Flow as my branching strategy with a master branch “always deployable”. I did, however, soon realize that this may not work very well for my scenario. I will talk more about this in the coming sections.

Branch Protection

Even though I was the only developer, I refrained from working on master. I added branch protection rules under GitHub settings to prevent pushing the commits directly to the master.

Figure: Branch protection rules

I then created my first issue and feature branch on GitHub to set up the project and CI build pipeline.

NuGet Account

I signed up at to publish my NuGet package. To publish the NuGet package to we need an API Key. The API key is a token that identifies a user to the NuGet gallery. I generated the API key from my newly created NuGet account.

Figure: API Key management for

The API key is a secret and should not be shared publicly. GitHub provides an ability to store secrets such as this under the Settings –> Secrets section which is where I ended up storing the key. The secrets can be accessed from the GitHub Action workflow as secure environment variables.

CI build Pipeline using GitHub Actions

The next step was to build a CI pipeline for the repository. I have quite some experience building the CI/CD pipeline on Azure DevOps but in this case I chose to try GitHub Actions, as I felt that it may provide seamless integration with the GitHub repository. And I was not wrong.

My GitHub Action workflow executes the following steps:

  • Versioning: Needless to say but a Nuget package requires versioning. I chose GitVersion to achieve Semantic Versioning on the project primarily because of the familiarity and experience of using it in my organization. The GitHub Action to use GitVersion can be found here.

Tip: When using GitVersion Action ensure that you have Gitversion.yml file in your source code to avoid unexpected issues. The documentation does not do a great job of explaining that. To configure additional options, refer to the source code.

  • Set up .NET Core: I used the official GitHub setup-dotnet Action to set up the dotnet cli environment. This action allowed me to use dotnet commands such as restore, build, test, pack, and nuget push.
  • Publish NuGet package: Pushing the package to was trivial. I used conditional steps to push the package only when the pull request is merged to the master. The API key was read from the GitHub secrets key-vault.

My CI workflow is available here.

I wanted to control when to push a new version to Unfortunately, one of the limitations of GitHub Action currently is the ability to manually trigger a workflow. It is one of the highest voted feature requests.

There are some hacks and workarounds available to achieve this but I did not spend much time exploring those options. In the longer term, I may switch to a Trunk-based development where I can have more control over my releases.


There some enhancements I’m looking to work on next as and when I have some spare time.

  • Ability to support multiple target frameworks. Currently, the package only supports .NET Core 3.1.
  • Change the branching strategy, have separate release branches.
  • Enhance GitHub actions, add features such as tagging, code coverage, code analysis, etc.
  • Release the major version of the NuGet package.


Publishing the NuGet package for my open source project was a unique experience. It was quite different from publishing NuGet packages for internal projects in my organization where we have more control. I intend to take these learnings and do similar projects in the future. I also hope that I was able to encourage some of you to take the first step into the world of open source and start working on your pet projects.

Source code:

NuGet package:


Please use the NuGet package and raise an issue to report a bug or feature request. Contributions are welcome :).


Created by

Ankit Vijay

Hi... I’m Ankit Vijay. I hold around 14 years of experience in application development & consulting. I’m a Dotnet Foundation member. I have worked in various roles ranging from Individual Contributor, DevOps, Solution Architect, Consultant, and Dev Lead depending on the nature of the project. I am passionate about technology and write about the topics I love. If you like my blogs, you can follow me on Twitter @ or GitHub @







Related Articles