Merge Team

The merge team is a group of developers from different teams of the Tezos ecosystem that controls what is merged into the repository. They are automatically selected as approvers when you create a merge request.

Merge Dispatcher

Every week, a dedicated member of the merge team, called the merge dispatcher, is in charge of making sure merge requests get merged. Their role is to:

  • make sure merge requests follow the MR workflow;

  • update labels;

  • ask people to review, fix issues, etc.;

  • make sure that merge requests are assigned to someone;

  • merge the merge requests that are ready.

Each week, Issue 1062 is re-assigned to the current merge dispatcher to make it easy to find out who it is. Don’t hesitate to contact the merge dispatcher if you need help to get your merge request moving.

Getting into the Merge Team

Admission to the merge team is done by cooptation. The merge team is always looking for software engineers with at least the following qualities:

  • You are an active developer on the tezos/tezos repository.

  • You have done numerous reviews and merge requests in the past, i.e. you have shown your expertise and interest in contributing both with code and reviews.

  • You are paying attention to detail and are on the lookout for possible errors, security issues, and/or enhancements in your reviews. It’s fine not knowing the entire codebase (no one does), but you should nevertheless actively try to make the code of others better when you do reviews.

  • You are well capable in software design and can identify subpar design choices.

  • One way to show attention to detail and to design is to show these qualities in your own merge requests. You should also be willing to amend your merge requests by taking into account the feedback of reviewers, be it for small changes or architectural changes.

  • You know when your expertise is insufficient and you are keen to ask for support.

  • You are relatively skilled in one of the technologies used in the tezos/tezos repository, i.e. OCaml, python, CI, building, packaging, etc.