Skip to content

Latest commit

 

History

History
77 lines (61 loc) · 2.32 KB

CONTRIBUTING.md

File metadata and controls

77 lines (61 loc) · 2.32 KB

Contributor Guide

Prerequisites

To work with the project, you'll need .NET SDK 8 or later.

Build

Use the following shell command:

$ dotnet build

Test

Use the following shell command:

$ dotnet test

Test Documentation

To open the project documentation site locally, use the following shell commands:

$ dotnet tool restore
$ dotnet docfx docs/docfx.json --serve

Then, open http://localhost:8080/ and browse the documentation.

License Automation

If the CI asks you to update the file licenses, follow one of these:

  1. Update the headers manually (look at the existing files), something like this: 
    // SPDX-FileCopyrightText: %year% %your name% <%your contact info, e.g. email%>
//
// SPDX-License-Identifier: MIT
    (accommodate to the file's comment style if required).
  2. Alternately, use REUSE tool: 
    $ reuse annotate --license MIT --copyright '%your name% <%your contact info, e.g. email%>' %file names to annotate%

(Feel free to attribute the changes to "TruePath contributors https://github.com/ForNeVeR/TruePath" instead of your name in a multi-author file, or if you don't want your name to be mentioned in the project's source: this doesn't mean you'll lose the copyright.)

File Encoding Changes

If the automation asks you to update the file encoding (line endings or UTF-8 BOM) in certain files, run the following PowerShell script (PowerShell Core is recommended to run this script):

$ pwsh -File scripts/Test-Encoding.ps1 -AutoFix

The -AutoFix switch will automatically fix the encoding issues, and you'll only need to commit and push the changes.

GitHub Actions

If you want to update the GitHub Actions used in the project, edit the file that generated them: scripts/github-actions.fsx.

Then run the following shell command:

$ dotnet fsi scripts/github-actions.fsx