# Contributing Thank you for your interest in contributing to Unity Multiplayer Networking! Here are our guidlines for contributing: * [Code of Conduct](#coc) * [Ways to Contribute](#ways) * [Issues and Bugs](#issue) * [Feature Requests](#feature) * [Improving Documentation](#docs) * [Unity Contribution Agreement](#cla) * [Pull Request Submission Guidlines](#submit-pr) ## Code of Conduct Please help us keep Unity Netcode for GameObjects open and inclusive. Read and follow our [Code of Conduct](CODE_OF_CONDUCT.md). ## Ways to Contribute There are many ways in which you can contribute to Netcode for GameObjects. ### Issues and Bugs If you find a bug in the source code, you can help us by submitting an issue to our GitHub Repository. Even better, you can submit a Pull Request with a fix. ### Feature Requests You can request a new feature by submitting an issue to our GitHub Repository. If you would like to implement a new feature then consider what kind of change it is: * **Major Changes** that you wish to contribute to the project should be discussed first with other developers. We will have a more formal process for this soon. For now submit your ideas as an issue. * **Small Changes** can be directly submitted to the GitHub Repository as a Pull Request. See the section about [Pull Request Submission Guidelines](#submit-pr). ### Documentation We accept changes and improvements to our documentation. Just submit a Pull Request with your proposed changes as described in the [Pull Request Submission Guidelines](#submit-pr). ## Contributor License Agreements When you open a pull request, you will be asked to enter into Unity's License Agreement which is based on The Apache Software Foundation's contribution agreement. We allow both individual contributions and contributions made on behalf of companies. We use an open source tool called CLA assistant. If you have any questions on our CLA, please submit an issue ## Pull Request Submission Guidelines We use the [Gitflow Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) for the development of the Netcode for GameObjects. This means development happens on the **develop branch** and Pull Requests should be submited to it. ### Commit Message Guidelines We have very precise rules over how our git commit messages can be formatted. This leads to **more readable messages** that are easy to follow when looking through the **project history**. We follow angular's message format. #### **Commit Message Format** Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes a **type**, a **scope** and a **subject**: ``` ():