Contributing to Fluent Assertions

No open-source project is going to be successful without contributions. After we decided to move to Github, the involvement of the .NET community has increased significantly. However, contributing to this project involves a few steps that will seriously increase the chance we will accept it.

• The Pull Request is targeted at the develop branch.
• The code complies with the Coding Guidelines for C#.
• The changes are covered by a new or existing set of unit tests which follow the Arrange-Act-Assert syntax such as is used in this example.
• If the contribution adds a feature or fixes a bug, please update the release notes, which is published on the website.
• If the contribution changes the public API, the changes needs to be included by running AcceptApiChanges.ps1/AcceptApiChanges.sh or using Rider's Verify Support plug-in.
• If the contribution affects the documentation, please update the documentation, under the appropriate file (i.e. strings.md for changes to string assertions), which is published on the website.