Podkrepi.bg Development
DocsWebsiteGitHub
latest
latest
  • Introduction
  • Dev Guidelines
    • Branching strategy
    • Pull requests guidelines
    • Starting a task
    • Definition of done
    • Recognising Contributions
  • Architecture
  • Backend
  • Frontend
    • Guidelines
      • React Guidelines
      • Translations (i18n)
      • Forms
    • Environments
      • .env
      • Local Development
      • Production
  • Infrastructure
    • Deployment to Kubernetes
  • REST API
    • Authentication
    • Endpoints
      • Healthcheck
      • Contact Request
      • Support Request
      • Campaigns
  • GRAPHQL
    • Schema
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Dev Guidelines

Branching strategy

The general approach to branching used within the organisation.

PreviousIntroductionNextPull requests guidelines

Last updated 4 years ago

Was this helpful?

Inherits the process from ​‌

​​🌞 Good branch names:‌

  • nice-kebab-cased-titles

  • fixes-footer-links

  • 4411290-setup-state-management-integration

  • feature/new-design

  • hotfix/db-connection

  • release-1.2.3

​​⛈ Bad branch names:‌

  • patch-1 - not enough context

  • camelCasedBranchNames - camelcase

  • PascalCasedBranchNames - pascal case

  • long-titles-above-80-chars-{.....} - too long

  • #58/something - shell understands it as comment

Branching model

Merges

​​​

​​​

https://nvie.com/posts/a-successful-git-branching-model/