Publish NuGet packages with Debug version of libgit2

Open
#16 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
powershell
Domain
build-system, release

Research direction

Start by reviewing the repository’s existing PowerShell packaging and publishing entry points, since the issue names no files or tests. Done means a reproducible NuGet package containing a Debug build of libgit2 is published, with the scheduled LibGit2Sharp usage considered in the package workflow.

Written by the indexing model from the issue text.

Description

This would greatly ease the job of troubleshooting libgit2 issues discovered through LibGit2sharp bug reports/regressions.

Another usage of this would be to allow us to run a weekly scheduled build of LibGit2Sharp leveraging https://github.com/libgit2/libgit2sharp/pull/1125 and finding potential libgit2 leaks with nice stacktraces.

/cc @jeffhostetler

Dominant language
PowerShell
Stars
35
Forks
74
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 libgit2/libgit2sharp.nativebinaries

All issues in libgit2/libgit2sharp.nativebinaries

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.