[READ THIS ISSUE] Development Guidelines

[vincenzosu]

1. Issues must always be opened against main. Don’t open issues like “this thing is broken on branch X”, when that branch is 10 commits behind and 38 changes ahead from main. It may also be useful to provide the hash of the latest commit when you open the issue.
2. Branches should live for the shortest time possible. As soon as you have a self-contained feature, open a pull request.
3. Once a pull request is open, finishing the review and merging it becomes top priority.
4. Don’t merge secondary branches into other secondary branches. First, it breaks rule 2. Second, it makes reviews a nightmare.
5. Before opening a pull request, make sure your changes are clean, no debug code.
6. Put some effort in refactoring code before opening a Pull Request. Garbage code can get your PR rejected.
7. I know, reviewing others’ code takes time and isn't the most exciting task, but it’s essential for a solid codebase. If you see a pull request with no requested changes that hasn’t been merged yet, it’s your turn to review it.