How is branching organized in the contracts repository — one main branch or several?

In the contracts repository, a main branch — usually called main (or master) — is typically used, which contains the current and stable version of the contracts. For developing new contracts or changes, separate feature branches are created, which are merged back into main after review and approval by the team.

This approach ensures centralized storage of contracts and simplifies version control. Sometimes, tags or separate branches are used to support multiple API versions, but this depends on the project requirements and release policies.