From be0961cda51b2a21e0e0214a992e76c0ceb60dc0 Mon Sep 17 00:00:00 2001 From: MohitMaliFtechiz Date: Fri, 5 Jan 2024 20:06:53 +0530 Subject: [PATCH] Added `backquotes` around the branch names. --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a082dd693..3e7053e03 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -45,8 +45,8 @@ Our process for accepting changes operates by [Pull Request (PR)](https://help.g Our branching strategy is based on [this article](https://nvie.com/posts/a-successful-git-branching-model/) which we suggest you read. + **main** the actively worked on next release of the app, what we branch off of while working on new features and what we merge into upon feature completion -+ **feature/** or feature/\/ any branch under this directory is an actively developed feature, feature branches culminate in a PR, are merged and deleted. - Typically a feature branch is off of main and into develop but in rare scenarios if there is an issue in production a branch may be made off main to fix this issue, this type of feature branch must be merged to main before being deleted. ++ **feature/** or feature/\/ any branch under this directory is an actively developed feature, `feature` branches culminate in a PR, are merged and deleted. + Typically a `feature` branch is off of `main` and into develop but in rare scenarios, if there is an issue in production a branch may be made off `main` to fix this issue, this type of `feature` branch must be merged to `main` before being deleted. Branch names should be in the format **\-kebab-case-title** All branches should have distinct history and should be visually easy to follow, for this reason only perform merge commits when merging code either by PR or when synchronising.