We love contributions. To get started contributing you might need:
- Get started with git
- How to create a pull request
- An issue to work on - We are
on Up for grabs, our up for grabs issues are tagged
up-for-grabs - An understanding of how we write tests
Once you know how to create a pull request and have an issue to work on, just post a comment saying you will work on it. If you end up not being able to complete the task, please post another comment so others can pick it up.
Issues are also welcome, failing tests are even more welcome.
- Try to use feature branches rather than developing on main
- Please include tests covering the change
- The docs are now stored in the repository under the
Docsfolder, please include documentation updates with your PR
It is easy to write tests in FluentAssertions.Autofac. Test fixtures are located directly beside the code in classes
ending with _Should.cs.
Find where your issue would logically sit, i.e. find the class closest to your issue.
We are currently using xUnit, so just create a descriptive test method and attribute it with [Fact].
Even better include the fix, but a failing test is a great start .