Skip to content

💡[Feature]: Add proper branching rules to have a consistent branch name patterns #910

@vansh-codes

Description

@vansh-codes

Is there an existing issue for this?

  • I have searched the existing issues

Feature Description

Add branching rules so that each branch depicts its purpose
For ex:
Bug fix branch can follow the pattern:
fix: #1 A bug fix

Feature branch:
feat: #1 A new feature branch

and so on..
docs, test, refactor, misc

Use Case

Consistent branching names across codebase & developers for consistency

Benefits

Consistent branch names across codebase, easy to maintain & adds readability

Add ScreenShots

No response

Priority

High

Record

  • I have read the Contributing Guidelines
  • Are you a GSSOC'25 contributor
  • I want to work on this issue

Metadata

Metadata

Assignees

Type

Projects

Status

In Progress

Relationships

None yet

Development

No branches or pull requests

Issue actions