Skip to content

Latest commit

 

History

History
74 lines (52 loc) · 3.65 KB

Contributing.md

File metadata and controls

74 lines (52 loc) · 3.65 KB
Raw
Table of Contents
Getting Started
Build & Run
Debugging
Coding Style
Branching

Getting Started

If you're authoring templates, or interested in contributing to this repo, then you're likely interested in how to use the latest version of this experience. The steps required are outlined below.

Prerequisites

  1. "git" (http://www.git-scm.com/) should be installed and added to PATH.

Acquire

  • Fork this repository.
  • Clone the forked repository to your local machine.
  • Checkout main and branch off to your feature branch (see: branching)
  • Rebase against main before submitting your PR.

Build & Run

  • Open up a command prompt and navigate to the root of your local repo.
  • Run the build script appropriate for your environment.

Debugging

This repo doesn't contain an executable application anymore. We recommend to do debugging using tests. Add your test scenario to the test project and debug it from IDE. To build, run and debug dotnet new, see the instuctions in dotnet/sdk repo.

Coding Style

Most of the styling is enforced by analyzers and the rules covered by the analyzers are not listed in this section. Therefore, it is highly recommended to use an IDE with Roslyn analyzers support (such as Visual Studio or Visual Studio Code).

  • We only use var when the variable type is obvious.
  • We avoid this, unless absolutely necessary.
  • We use _camelCase for private fields.
  • Use readonly where possible.
  • We use PascalCasing to name all our methods, properties, constant local variables, and static readonly fields.
  • We use nameof(...) instead of "..." whenever possible and relevant.
  • We use nullable reference types to make conscious decisions on the nullability of references, be more clear with our intent and reduce NullReferenceExceptions. Add #nullable enabled to the top of all the modified files unless:
    • Nullable reference types are already enabled for the file
    • The file is in one of the test projects
    • The changes you are introducing to the file are negligable in size compared to the size of the whole file,
    • You don't have enough context on the code to make decisions on nullability of types.

Some of the analyzer rules are currently being treated as "info/suggestion"s instead of "warning"s, because we have not yet done a solution wide refactoring to comply with the rules. Although it would be most welcome, you are not required to fix any of the existing suggestions. However, any code that you introduce should be free of suggestions.

Top

Branching

We do development in main branch. After a release branch is created, any new changes that should be included in that release are cherry-picked from main.

We follow the same versioning as https://github.com/dotnet/sdk and release branches are named after the version numbers. For instance, release/5.0.2xx branch ships with .NET SDK 5.0.2xx.

Topic Branch
Development main
Release release/*

Ways to contribute

Top