To work with the project, you'll need .NET SDK 8 or later.
Use the following shell command:
$ dotnet buildUse the following shell command:
$ dotnet testOn Windows, tests that create symbolic links require either Developer Mode or an elevated
process. Developer Mode lets an unelevated process create symbolic links, as documented for the
CreateSymbolicLinkW API. When neither is available, these tests are skipped locally; CI
runners fail instead, ensuring that the tests are not silently skipped in automation.
To open the project documentation site locally, use the following shell commands:
$ dotnet tool restore
$ dotnet docfx docs/docfx.json --serveThen, open http://localhost:8080/ and browse the documentation.
If the CI asks you to update the file licenses, follow one of these:
- Update the headers manually (look at the existing files), something like this:
(accommodate to the file's comment style if required).
// SPDX-FileCopyrightText: %year% %your name% <%your contact info, e.g. email%> // // SPDX-License-Identifier: MIT
- 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.)
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 -AutoFixThe -AutoFix switch will automatically fix the encoding issues, and you'll only need to commit and push the changes.
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