Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Publish OpenApiDiff to Nuget (or make dotnet cli tool)

Open
#151 2 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
32/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, node.js
Domain
api, cli, release

Research direction

Start by inspecting the existing Node package and the command-line entry point for OpenApiDiff. Determine how a NuGet package or .NET CLI tool would be built and published without requiring Node; done means users can install and run it from a .NET-based build pipeline and the published artifact is documented.

Written by the indexing model from the issue text.

Description

Having this tool as a node package is great... but having it as a nuget package or dotnet CLI tool would be even better for those of us who have API's without javascript frontends. Otherwise I need to add node to my build pipeline in order to use it.

Dominant language
C#
Stars
290
Forks
50
Avg merge
2d 21h
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/openapi-diff

All issues in Azure/openapi-diff

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.