Project setup from the template repository
Use the project template to initialize a new repository, or adapt an existing one copying its file and structure. Then follow this checklist to adapt the template to your project.
Build system
- Update the build configuration in
build/orchestrator/Program.cswith your project settings (e.g. code coverage or warnings as errors).
.NET project
- Rename, edit, remove the project folders inside
src/and the solution file. - Edit the project name and URL in
src/Directory.Build.props - Add, remove, update dependencies in
src/Directory.Packages.props - Update the
.csprojfiles with the correct dependencies. - Update
build/orchestrator/Program.cswith the list of publishable .NET projects inApplicationProjects. - Update
build/orchestrator/Program.cswith the production and preview NuGet feeds, or remove to use nuget.org.
Documentation
- Update the icons of the project at
docs/images/. - Update
docs/index.mdwith project information - Update
docs/articleswith the desired documentation layout. - Update
docs/docfx.jsonwith the path to the API project files. - Update
docs/docfx.jsonwith the project metadata - Update
docs/toc.ymlanddocs/template/public/main.jswith the project URL.
Continuous integration
- Create secret variables with the NuGet tokens in the GitHub project settings
- Pass your variable's name in the inputs
nuget_stable_token,nuget_preview_tokenorazure_nuget_token - Review
build.ymlto remove / add OS platforms to run build and tests. - Enable GitHub Pages in the repository settings
- Pages -> Select GitHub Actions as the source.
- Environments -> github-pages -> Add new rule for tags
v*
- Allow to add release artifacts and publish docs with the built-in GITHUB_TOKEN via: Actions -> General -> Workflow permissions -> Read and write permissions
Collaboration files
- Update
README.mdtitle and description. - Update
LICENSEwith your desired license and copyright info - Update VS Code
.vscode/launch.jsonwith the path of the console application (if any).