Once you are happy with the changes you've made, you need to commit them. To do this, you need to fill in the fields at the bottom of the editor and hit "Commit changes". But it is important to fill the fields out correctly!
This is a free text message that you can use to explain your changes to other people (including Future You). The Forge will automatically populate this with a suggestion, but if possible replace it with something short and descriptive.
This one is important. You need to make sure you commit your changes to the branch you created earlier. If this isn't set correctly, click on the box and select your branch from the drop-down list.
When you are ready, hit the green "Commit changes" button. This will commit your change.
Now you have commited your change, other people can see and comment on it. The Forge can also run a set of automated checks on the changes you've made. Look out for a little icon that tells you whether your commit has passed these checks or not. If it fails, click on the icon to find out more about why it failed.
The automated checks are a work in progress. Right now they only check simple ASN.1 syntax; modules are not compiled. XSD files are not checked at all.
If you need to make further changes, repeat step 5 and 6 as often as you need until you are happy that you can propose your CR.
When you are ready to submit your CR for consideration to the meeting, go to the next step to learn how to make a merge request.