Overview

If you are interested in contributing changes you have made to the engine back to the main repository on Github, this article helps users go through the process of submitting those changes (Pull Requests).

Please note that this step is entirely optional, and only applies when engine changes have been made.

This article assumes that users already have the following:

• An account with GitHub
• Installed the GitHub Desktop for Windows application on their PC
• Read and understood the following: Crytek coding guidelines and Crytek commit description rules

Workflow

CRYENGINE users must submit their pull requests to a branch named pullrequests in the Crytek GitHub repo. Any pull request that is submitted to any other Crytek branch will not be accepted by Crytek. Once a pull request is accepted it will be evaluated by Crytek and any comments made can be seen via GitHub. All users should monitor the channel to follow the progress being made in regard to their submission.

Submission Steps

1. Go to the Crytek GitHub repo (this is GitHub.com) and sign in. This will open the Crytek/CRYENGINE repo.
   
2. Fork the Crytek repo by clicking on the icon. You maybe be asked "Where should we fork this repository?" In almost all cases this will be to the account that you have just signed in to. In the example(s) used below, the account is named Cry-Doug and the name of the repo that will be/has been created is made up of the account name and CRYENGINE. Hence, we will have a repo named Cry-Doug/CRYENGINE.
3. We now need to clone a repo, so open the GitHub desktop application (use the icon on your PC desktop). This opens the following screen:
   
   Now click the Clone a repository button, the screen in step 4 will open.
   
   
4. You now need to enter the name of your repo (in the URL or username/repository field). In our example it will be Cry-Doug/CRYENGINE. You can also change the Local path as you desire. In our case we have chosen the D: Drive of our PC. NOTE: We strongly recommend that if you want to compile Engine code that you save your repo on an SSD. Finally, click the Clone button.
   
   
   
5. We now have a cloned repo named Cry-Doug/CRYENGINE. This can be seen be navigating back to https://github.com/Cry-Doug/CRYENGINE.
   
   
   
6. Navigate to the GitHub Desktop application. You now need to switch the Current branch from release (using the drop down menu) to origin/pullrequests. Changing to pullrequests is ESSENTIAL!!
   
   
   
7. The next step is to create your own branch. So from the menu options, click Branch -> New branch... and give your Branch a name. In the example below we have named our branch Docs_Test. Finally, click the Create branch button.
   
   
   
8. This will open the screen shown below:
   
   
   
9. You now need to make your changes. i.e. the ones that you want to submit to Crytek. This could be acheived with a variety of tools such as Notepad or VS etc... In our example we have just added the words CHANGE CHANGE CHANGE to the README.md file. This can file can be found (in our case on our D drive. See step 4 above).
10. Once you have made your changes, go back to the GitHub desktop application. You will see that GitHub Desktop automatically detects the change(s) that you have made (screenshot below).
11. Ensure that any file(s) that you want to commit/submit to Crytek are ticked. Then add a summary. This is a requirement, whereas the description is optional. Finally, click the Commit button (in our case Commit to Docs_Test).
12. We now need to publish the branch, so click the Publish branch button.
    
    
    
13. We now need to get our branch to Crytek. Create a pull request using the menu option Branch -> create pull request (you may need to login to GitHub). This will open the window shown below:
    
    
    
14. You must then change base: to pullrequests (use the drop down). Also ensure that the title entered meets the Crytek commit rules.
15. Finally, click the Create the pull request button. This will trigger the review process on Crytek's end.
16. The submitter will be notified by email of any changes/updates made.