Git + .Net/Mono = ❤
Перейти к файлу
Markus Olsson 37802e5cfc Fix relative path to solution 2015-11-03 02:20:12 +01:00
.nuget
CI Explicitly set xUnit MSBuild WorkingFolder property 2015-07-04 18:19:16 -04:00
Lib GenerateNativeDll task: use file name from nuget 2015-08-23 15:47:53 +02:00
LibGit2Sharp Fix relative path to solution 2015-11-03 02:20:12 +01:00
LibGit2Sharp.Tests Upgrade xunit.runner.visualstudio NuGet package to 2.1.0 2015-10-03 12:57:56 +02:00
nuget.package
.editorconfig
.gitattributes
.gitignore
.mailmap
.travis.yml
CHANGES.md
LICENSE.md
LibGit2Sharp.sln
LibGit2Sharp.sln.DotSettings
LibGit2Sharp.v2.ncrunchsolution
README.md
acknowledgments.md
appveyor.yml Leverage APPVEYOR_REPO_COMMIT_TIMESTAMP as build date 2015-07-14 13:04:38 +02:00
build.libgit2sharp.cmd
build.libgit2sharp.sh
square-logo.png

README.md

LibGit2Sharp

LibGit2Sharp brings all the might and speed of libgit2, a native Git implementation, to the managed world of .NET and Mono.

Prerequisites

  • Windows: .NET 4.0+
  • Linux/Mac OS X: Mono 3.6+

Online resources

Troubleshooting and support

  • Usage or programming related question? Post it on StackOverflow using the tag libgit2sharp
  • Found a bug or missing a feature? Feed the issue tracker
  • Announcements and related miscellanea through Twitter (@libgit2sharp)

Current project status

The CI builds are generously hosted and run on the Travis and AppVeyor infrastructures.

Windows (x86/amd64) Linux/Mac OS X
master master win master nix
vNext vNext win vNext nix

The security-oriented static code analysis is kindly run through the Coverity service. Code coverage is kindly run through Coveralls.io.

Static Analysis Code Coverage
vNext coverity coveralls

Quick contributing guide

  • Fork and clone locally
  • Create a topic specific branch. Add some nice feature. Do not forget the tests ;-)
  • Send a Pull Request to spread the fun!

More thorough information available in the wiki.

Optimizing unit testing

LibGit2Sharp strives to have comprehensive and robust unit test suite to insure the quality of the software and to assist new contributors and users who can use the tests as sample to jump start development. There are over one-thousand unit-tests for LibGit2Sharp, this number will only grow as functionality is added.

You can do a few things to optimize running unit-tests on Windows:

  1. Set the LibGit2TestPath environment variable to a path in your development environment.
  • If the unit-test framework cannot find the specified folder at runtime, it will fall back to the default location.
  1. Configure your anti-virus software to ignore the LibGit2TestPath path.
  2. Install a RAM disk like IMDisk and set LibGit2TestPath to use it.
  • Use imdisk.exe -a -s 256M -m X: -p "/fs:fat /q /v:ramdisk /y" to create a RAM disk. This command requires elevated privileges and can be placed into a scheduled task or run manually before you begin unit-testing.

Authors

License

The MIT license (Refer to the LICENSE.md file)