Add page describing current branching policies

[Pinolo]

In "procedures" or "guides" section?

Information should reflect what has been done in https://gitlab.sparkfabrik.com/sparkfabrik-innovation-team/board/-/issues/108 (only accessible by SF staff), and any other relevant information about common branching policies, associated with CI/CD

[stickgrinder]

Guides section is for broader treatment of a topic, while Procedures contains basically "checklists and recipes" that you can follow top-to-bottom.

A good example for disambiguation is:

• https://playbook.sparkfabrik.com/guides/an-effective-onboarding-structure (guide)
• https://playbook.sparkfabrik.com/procedures/employee-onboarding (procedure)

Can you spot the difference?

[Pinolo]

It looks more "guides" to me. What do you think?

[stickgrinder]

If it is supposed to be a rule that we MUST implement, having at least a short companion procedure to set things up (or a checklist to refer to) is a boon.

If it is an informative page, helping people finding a common ground and then things may evolve from there freely (like it should be in a dynamic env) a guide is ok.

Mind that we already have a page related to git procedures: https://playbook.sparkfabrik.com/procedures/git-rebase-workflow
This is obviously a sub-subset of the topic but you may want to take this into consideration and possibly integrate it with the guide or create other procedures to complete this?