... | ... | @@ -16,6 +16,17 @@ Due to quirks with GitLab's permission system, when you make a fork we don't hav |
|
|
|
|
|
Make sure you reach out on [the Discord](https://redpoint.games/support) to coordinate your merge request with us. This will allow us to tell you when we expect we'll be able to review it, and to make sure your approach is generally correct before you implement your changes.
|
|
|
|
|
|
### 5. Submit your merge request
|
|
|
### 5. Implement your changes
|
|
|
|
|
|
Make your changes in your fork.
|
|
|
|
|
|
### 6. Check tests and auto-format your code
|
|
|
|
|
|
Some repositories have automated tests and some repositories have code formatting / style guidelines. Make sure you merge request complies with both of the following before submitting:
|
|
|
|
|
|
- You've run `.\BuildScripts\Format.ps1` in the repository, if it exists. You can also set up clang-format within Visual Studio and install the "Format on Document Save" extension which will help keep your code compliant with the styling at all times.
|
|
|
- You've run `.\BuildScripts\Build.ps1 -ThenTest` in the repository. Check the `.gitlab-ci.yml` file for the specific arguments you can use with this; usually you just need to pass `-Engine` for the engine version and `-Distribution` for the distribution to target.
|
|
|
|
|
|
### 7. Submit your merge request
|
|
|
|
|
|
Once you've done the above and implemented your changes, submit your merge request. |
|
|
\ No newline at end of file |