You are thinking about contributing to .NET Testcontainers? Awesome, it’s absolutely appreciated. When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change. Or pick an already existing issue.
To build the project just run the provided Cake script, ./build.sh
(Unix) or .\build.ps1
(Windows).
- Fork the .NET Testcontainers repository.
- Create a branch to work with and use
feature/
orbugfix/
as a prefix. - Do not forget the unit tests and keep the SonarCloud statistics in mind.
- If you are finished rebase and create a pull request.
- Cheers, 🍻.
.NET Testcontainers uses a consitent and structured vocabulary for commit messages with the following pattern:
[ISSUE] #LABEL 'specification'
{Comment}
- #INIT: Initializes a repository or a new release
assemblyName
: assembly nameversion
: version
- #IMPLEMENT: Implement a new function
assemblyName
: assembly namefunction
: class
- #CHANGE: Change an existing function
assemblyName
: assembly namefunction
: class
- #EXTEND: Extend an existing function
assemblyName
: assembly namefunction
: class
- #BUGFIX: Bugfix
assemblyName
: assembly name
- #REVIEW: Quality control
assemblyName
: assembly namerefactor
: functionanalyze
: qualitymigrate
: functionformat
: source
[1] #INIT 'assemblyName: DotNet.Testcontainers; version: 1.0.0'
[2] #IMPLEMENT 'assemblyName: DotNet.Testcontainers; function: TestcontainersClient'
{Add Dockerfile support.}
[3] #CHANGE 'assemblyName: DotNet.Testcontainers; function: TestcontainersConfiguration'
{Change default wait strategy to WaitUntilContainerIsRunning.}
[4] #EXTEND 'assemblyName: DotNet.Testcontainers; function: TestcontainersConfiguration'
{Add new configuration property WaitStrategy.}