<commit_before># How to contribute to Hyprlinkr

Hyprlinkr is currently being developed in C# on .NET 4.5 using Visual Studio 2013 with xUnit.net as the unit testing framework. So far, all development has been done with TDD, so there's a high degree of code coverage, and it would be preferable to keep it that way.

## Dependencies

All binaries (such as xUnit.net) are included as NuGet packages in the source control repository under the \packages folder. All additional binaries not part of .NET 4.5 must also be added to the repository, so that it would be possible to pull down the repository and immediately be able to compile and run all tests.

Hyprlinkr does [not rely on NuGet Package Restore](http://blog.ploeh.dk/2014/01/29/nuget-package-restore-considered-harmful).

## Verification

There is currently a single solution to be found under the \Src folder, but be aware that the final verification step before pushing to the repository is to successfully build the BuildRelease.msbuild file. This can be done either from Bash (using build-release.sh) or PowerShell (using BuildRelease.ps1).

As part of the verification build, Visual Studio Code Analysis is executed in a configuration that treats warnings as errors. No CA warnings should be suppressed unless the documented conditions for suppression are satisfied. Otherwise, a documented agreement between at least two active developers of the project should be reached to allow a suppression of a non-suppressable warning.

## Pull requests<commit_msg>Correct name of Build-Release PowerShell script<commit_after># How to contribute to Hyprlinkr

Hyprlinkr is currently being developed in C# on .NET 4.5 using Visual Studio 2013 with xUnit.net as the unit testing framework. So far, all development has been done with TDD, so there's a high degree of code coverage, and it would be preferable to keep it that way.

## Dependencies

All binaries (such as xUnit.net) are included as NuGet packages in the source control repository under the \packages folder. All additional binaries not part of .NET 4.5 must also be added to the repository, so that it would be possible to pull down the repository and immediately be able to compile and run all tests.

Hyprlinkr does [not rely on NuGet Package Restore](http://blog.ploeh.dk/2014/01/29/nuget-package-restore-considered-harmful).

## Verification

There is currently a single solution to be found under the \Src folder, but be aware that the final verification step before pushing to the repository is to successfully build the BuildRelease.msbuild file. This can be done either from Bash (using build-release.sh) or PowerShell (using Build-Release.ps1).

As part of the verification build, Visual Studio Code Analysis is executed in a configuration that treats warnings as errors. No CA warnings should be suppressed unless the documented conditions for suppression are satisfied. Otherwise, a documented agreement between at least two active developers of the project should be reached to allow a suppression of a non-suppressable warning.

## Pull requests
{'fraction_non_alphanumeric': 0.042926829268292686, 'fraction_numerical': 0.011056910569105691, 'mean_word_length': 4.613138686131387, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2171735', 'n_tokens_mistral': 757, 'n_tokens_neox': 711, 'n_words': 454}