As some people already said there's:
- Git-Flow (5-branches model)
- The 3-branches way: master (working and production ready code), develop (code being currently developed), feature_feature-name (temporary branch dedicated to the development of a feature)
- The 2-branches ways (here's 3 that are quit popular):
- master (used for development and up-to-date code), release-[version_name/number] (used for stable releases)
- production (for production ready code often known as master), develop
- master, task-[name/number] (task viewable on a file containing a list of tasks, e.g: ToDo.md, Tasks.md, README.md, ...)
Of course, there's plenty other ways to name branches according to how your workflow is set up and what branch should contain what and how accessible each of those branches are.