A pull request means that you request the project maintainer to pull/include the changes you made into the main project. Before talking about how this is done technically, let us have a look on the politics/collaboration part behind this.

Etiquette

The main goals of the etiquette are:

1. To prevent that you put time and effort in work, that is not accepted by the project maintainer.

2. To track the work that is done in a way that it shows up in release notes.

Communicate, before you start

Before you actually start your work, ask the project maintainer whether they agree with the change/addition you are planning. A good way to do that is via Slack, which is explicitly used for contributor communication.

If the scope of your work is discussed - latest before you create a pull request - ask the maintainer to create an internal Jira ticket for your task and receive a ticket identifier (e.g. SR6-56)

Add the ticket identifier in your commit messages

Having the ticket in the first line of your commit message, helps that all changes made to the code can be related to a specific task. E.g. if your commit message is “SPLIMO-58” , the tools would list this as follows:

Creating a pull request

When your work is done and you a fairly sure and you verified that it is working as expected, it is time to let the maintainer include your code. Go the the webpage of the repository and navigate to “Pull requests”. In the upper right section of the screen, is a button to create a new pull request.

In the upcoming dialog, you need to select which of your branches you want to be pulled and which branch (usually “master”) of the main project it should be merged into.

In the title, enter the ticket identifier the maintainer gave you (see above). If you want a specific reviewer, you can define the person too.

If you hit the “Create pull request” button, the project maintainers are informed that there is a request waiting. We can’t make any promises on how fast we are reviewing it.