There is the Contributing page which covers quite a lot of different things, including submitting patches. The way that most repositories are set up on source.puri.sm means that you can’t push to the master branch. Usually, you have to follow these steps:
- Fork the repository on source.puri.sm so that your account has a copy of it.
- Clone the repository locally.
- Create a branch for the changes you want to make, then make the changes:
git checkout -b <name>
name is something meaningful.
- Commit the changes.
- Push the commit back to your fork at source.puri.sm:
git push origin <name>
name is the branch name you used.
This last step should result in a message telling you how to make a merge request for your changes.
There is another way to do things but I think the workflow is not quite optimal. This is to create an issue first, then create a merge request for that issue by clicking the Create merge request button. However, I think the instructions it gives when you click the Check out branch button are not correct for the workflow we have.
A workaround that might be easier is to create an issue in your own fork of the repository, then click Create merge request for that issue. Unfortunately, that wouldn’t help for existing issues.